Workflow (CI‐CD)

Workflows

• The workflow Dispatch (CI/CD) runs on every push (branch main or tag v*) and decides what to trigger based on the ref/commit message
• The workflow Unit Tests - Libraries (CI) builds the unit tests and execute them
• The workflow Build - Packages (CI/CD) builds the packages (.rpm/.deb) and syncs/releases them
• The workflow Build - Libraries (CI) only builds the libraries and checks the compilation, without producing or releasing packages

Important

Any dispatch to Build workflows depends on the result of Unit Tests - Libraries (CI). If any unit tests fail, the pipeline is discontinued.

Note

Only when Dispatch (CI/CD) decides not to build packages, the Build - Libraries (CI) workflow runs instead, to validate that the code still compiles

Pre-Release (unstable)

Depends on Unit Tests - Libraries (CI) result

The pre-release of the packages can be triggered by 2 events:

• Pushing a tag that matches the regex vx.x.x-pre (x stands for the version number: major, minor, fix)
• Or pushing a commit containing the string [build], preferably in the description

Release (stable)

Depends on Unit Tests - Libraries (CI) result

The release of the packages (channel stable) can only be triggered by pushing a tag that matches the regex vx.x.x-release (x stands for the version number: major, minor, fix)

Downstream notification

Depends on Build - Packages (CI/CD) result

In addition to building/publishing, Dispatch (CI/CD) notifies the docker-image repository (via repository_dispatch) whenever a release is decided:

• Pushing a tag matching vx.x.x-release
• Or pushing a commit containing the string [release], preferably in the description