CI

The Manifesto

A Continuous Integration manifesto that helps describe the goals, terminology, and rules.

Tests locations

The tests to be executed are stored in the dist-git repositories]. The tests are stored or wrapped along-side the spec files that describe the software sources. The tests are branched, maintained along with the package or module they pertain to.

Package or RPM specific tests are stored in that package's repository. Such package repositories will have a rpms/ prefix in their name. Other tests refer to larger sets of functionality, called modules and are in a dist-git repository with modules/ prefix in their name.

• To checkout a dist-git repo, use fedpkg tooling.
• To contribute tests to a dist-git repository get a Account.
• Use Pagure.io to contribute to a dist-git repository using a GitHub style interface.
  • Ready: July 5, 2017
  • Contact: Pierre Yves-Chibon
• To move or wrap downstream tests to Fedora, use https://upstreamfirst.fedorainfracloud.org/
  • Contact: Tim Flink

Test format

Tests may be written all sorts of different ways, but have to be exposed and invoked in a standard way. They are stored or wrapped in the tests/ directory in a dist-git repository. There is a detailed description of how this is done:

• Standard Spec for Invoking Tests

Gating

When a test fails, continuous integration will be able to prevent the broken package change from affecting other changes. That gating will happen in Bodhi. Packages in the core operating system, such as those in Atomic Host are most interesting for gating, as when they break they affect the most users.

• Modules and packages will be able to opt into gating.
• Proposals and options
• Ready: August 2017

Testing pipeline

The pipeline is under development

• Source Code: https://github.com/CentOS-PaaS-SIG/ci-pipeline
• Documentation: https://github.com/CentOS-PaaS-SIG/ci-pipeline/blob/master/README.md
• More pipeline description
• Build options and ideas
• Possibilities for upstream open-source project integration