Continuous Integration

The continuous integration in Kratos is done with Github Actions.

Current configurations

Different configurations are compiled and tested, e.g. with GCC and CLANG under Linux and MSVC under Windows For details please check the workflows folder

CI check before merging pull requests

• Compiled in

• Required checks

• Not required checks

• Skipping workflow runs

  See the official documentation

Nightly build

Rules for adding an application to the CI

For adding a new application to the CI, the Technical Committee decided that the following is required (see here):

• The Application must have tests
• Having at least two maintainers providing continuous support in case of CI failure. In case of no support the application would be removed from the CI.
• There are timers which limit the testing time for each applications (1 minute per Application for small tests, 15 minutes per Application for nightly tests). So the total CI time cannot be abused by one application. Please note that the CI machine is considerably slower than a normal desktop.

So applications which want to be part of the CI can create a PR adding the application to it. These PRs should be approved by the Technical Committee.

FAQ

• How to restart a build? https://docs.github.com/en/actions/managing-workflow-runs/re-running-a-workflow

• How to check a branch without opening a pull request https://docs.github.com/en/actions/managing-workflow-runs/manually-running-a-workflow => currently supports CI and Nightly Build

• Cancelling (redundant) builds Also mention: https://docs.github.com/en/actions/managing-workflow-runs/canceling-a-workflow

• Checks are failing even though I didn't modify this part of the code

For developers

• Where to find the files? here
• Reference Documentation
• Supported runners and hardware resources
• Supported software