This repository contains some of the pipelines of Kogito project.
Apart from this repository, pipelines are also concerning those repositories:
Kogito has 2 main pipelines:
- Nightly pipeline
is a multibranch pipeline which is run daily on each active branch - Release pipeline
is a on-demand single pipeline job
More information can be found here.
This is a set of cleanup utils jobs.
In some of the Kogito repositories, you can find native checks. If that is the case, the pipeline can be found in .ci/jenkins/Jenkinsfile.native.
Quarkus and Native checks are also performed against Mandrel builder image (see config mandrel.builder_image).
A nightly check against Quarkus is done every night. Pipeline can be found in https://github.com/kiegroup/kogito-runtimes/blob/main/.ci/jenkins/Jenkinsfile.quarkus.
PR checks are using the build-chain for artifacts and its configuration can be found in .ci folder.
They are run on both Jenkins and GHA with some slight differences.
There is one check per downstream repository. This allows parallelization and more flexibility in restart of a specific downstream repo.
kogito-images is run only on Jenkins and is using its own .ci/jenkins/Jenkinsfile.
kogito-operator is run on another Jenkins and is using its own .ci/jenkins/Jenkinsfile.
The jobs can be found into the {branch}/pullrequest folder in Jenkins.
Each repository contains the needed DSL configuration (can be found in .ci/jenkins/dsl) and will most of the time use the KogitoTemplate method createMultijobPRJobs.
This will generate all the needed PR checks and make use of the Jenkinsfile.buildchain file.
Jenkins PR checks are of 3 different types:
- Simple build&test (automatic)
Regular testing - Native build&test (optional, can be launched with comment
jenkins run native)
Test all native parts of the repository - Mandrel build&test (optional, can be launched with comment
jenkins run mandrel)
Test against Mandrel builder image - Quarkus main build&test (optional, can be launched with comment
jenkins run quarkus-main)
Test against quarkus main version - Quarkus branch build&test (optional, can be launched with comment
jenkins run quarkus-branch)
Test against quarkus branch, corresponding to current used Quarkus released version - Quarkus lts build&test (optional, can be launched with comment
jenkins run quarkus-lts)
Test against quarkus branch, corresponding to current used Quarkus LTS version
Each repository has a different yaml files in .github/workflows folder to configure the workflow.
We are additionally using composite actions to centralized most common steps used by the different Kogito repositories' jobs. You can check the different kind of composite actions we have available at .ci/actions folder.
After the build, test results are parsed and logged using the action-surefire-report action.
NOTE: test coverage analysis is executed only by Jenkins PR simple build&test and not while using GitHub action.
All pipelines can be found in kogito Jenkins folder.
More information can be found here.
Any message / error is sent to kogito-ci stream.
[branch] Project