| commit | d820c49726302f7d26ac1b4109176a2f42030fcc | [log] [tgz] |
|---|---|---|
| author | Toshiya Kobayashi <toshiyakobayashi@gmail.com> | Fri Dec 13 02:05:02 2024 +0900 |
| committer | GitHub <noreply@github.com> | Thu Dec 12 12:05:02 2024 -0500 |
| tree | f86e61fe569cf563573cb0abb95c1480de4a250b | |
| parent | 1da93ff1c0f6a65f6fa868cd4fd729e6f417d8ea [diff] |
[incubator-kie-issues-1618] notice file in root of source release (10.0.0 - RC3) has wrong year in it (#1272) - Clean up third party entries - year with range
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:
More information can be found here.
This is a set of cleanup utils jobs.
The jenkinsfile run in those environments can be found in each repository, at path .ci/jenkins/Jenkinsfile.specific_nightly.
The different environments can also be found into the dsl branch config file.
Here is some explanation:
nativemandrelquarkus branchquarkus mainquarkus ltsmandrel ltsAs an experimentation, due to many conflicts with quarkus lts and quarkus main branches, it has been decided to try to use an integration branch for the those nightly checks, in order to be able to resolve conflicts that my occur, but which cannot be pushed directly to the tested branch.
The integration branch nightly will:
-no-ff)Those new nightly jobs are currently set up as new jobs and won't replace the current ones without the integration branch.
Once we decide, we may remove the “old” jobs and use only the integration branch.
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.
NOTE: PR checks are also available for the different environments listed above. Please read the PR template to know which one are available for a specific repository.
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:
jenkins run native)jenkins run mandrel)jenkins run quarkus-main)jenkins run quarkus-branch)jenkins run quarkus-lts)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.
Note: Creating separate readme.md documenting how-tos and best practices for implementing pipelines might be useful
In this repository two types of pipelines can be found:
Apart from these pipelines, the jenkins-pipeline-shared-libraries are also stored in this repository. Functions and classes contained in these libraries can be freely used in all pipelines located under KIE Jenkins folder. Just include correct import and annotation in your Jenkinsfile:
import org.jenkinsci.plugins.workflow.libs.Library
@Library('jenkins-pipeline-shared-libraries')_
For more details please see our Jenkins pipelines shared libraries documentation and Jenkins.io documentation
All KIE jobs (pipelines) can be found in KIE Jenkins folder
For this folder and all its descendants there is several useful things set at this folder level:
jenkins-pipeline-shared-libraries it gives access to some useful functions used throughout various KIE pipelines. More details can be found in our Jenkins pipeline shared libraries documentation and in the previous chapterConfigure in the left menu (if you have necessary permissions). Currently present Environment Variables are:util.avoidFaultyNodes(String label), which extends desired label by expression that ensures avoiding these faulty nodes. Use of util.avoidFaultyNodes() (without parameter) is also possible for cases where no specific label needs to be set. This way we can increase durability of KIE automation by the time the Apache CI team fixes the issue with faulty node.All pipelines from this repository can be found in kogito Jenkins folder.
More information can be found here.
Any message / error is sent to kogito-ci stream.
[branch] Project
The work on the pipelines has been separated into different epics:
Please use one of those epics if you create any issue.