tomasdavidorg / kogito-pipelines

CI/CD pipelines for Kogito

Kogito Pipelines

This repository contains some of the pipelines of Kogito project.

• Kogito Pipelines
• Kogito Repositories
• The different Kogito pipelines
  • Nightly & Release pipelines
  • Tools pipelines
  • Repositories' specific pipelines
    • Kogito Runtimes' other jobs
    • PR checks
      • Jenkins checks
      • GitHub Action checks
    • Sonar cloud
• Configuration of pipelines
  • Jenkins
    • Jenkins jobs generation
  • Zulip notifications
    • Format

Kogito Repositories

Apart from this repository, pipelines are also concerning those repositories:

• kogito-runtimes
• optaplanner
• kogito-apps
• kogito-examples
• kogito-images
• kogito-operator

The different Kogito pipelines

Nightly & Release pipelines

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.

Tools pipelines

This is a set of cleanup utils jobs.

Repositories' specific pipelines

Kogito Runtimes' other jobs

Those jobs can be found into the kogito-runtimes repository.
They are daily run jobs:

• kogito-native
  Perform a daily native build&test of runtimes.
• kogito-quarkus
  Perform a daily check of runtimes against latest snapshot of Quarkus.
• kogito-drools-snapshot
  Perform a daily check of runtimes against latest snapshot of Drools.

PR checks

For each PR there are two different CI builds, one using internal Jenkins executor and another one that leverage GitHub actions.

Jenkins checks

Each repository has a Jenkinsfile for the PR check.

The jobs are located into the pullrequest folder in Jenkins.
Only the Operator PR check is not yet in this folder as it is still on another Jenkins

GitHub Action checks

Each repository has a ci-pr.yaml file in .github/workflows folder to configure the workflow. The kogito-runtimes repo has a different configuration, see additional notes at the end of this paragraph.

Repo dependencies and build commands are configured in the centralized .ci folder in this repo.

Build execution is performed using the github-action-chain action that automatically performs cross repo builds.

After the build, test results are parsed and logged using the action-surefire-report action (actually we are using a forked version until this PR #56 will be accepted).

Additional notes about kogito-runtimes build: this repo requires a full downstream build of all the repositories so to minimize disk usage and execution time the repo has been configured to use multiple jobs in parallel, one for each repo. This means that instead of a single ci-pr.yaml file, there are four of them: runtimes-pr.yaml, optaplanner-pr.yaml, apps-pr.yaml and examples-pr.yaml. For each of them all upstream repos are just compiled without test execution.

Sonar cloud

NOTE: test coverage analysis is executed only by Jenkins PR build and not while using GitHub action

Configuration of pipelines

Jenkins

All pipelines can be found in kogito Jenkins folder.

Jenkins jobs generation

More information can be found here.

Zulip notifications

Any message / error is sent to kogito-ci stream.

Format

[branch] Project