From Fedora Project Wiki

(Moved continuous integration info to this page. Checked with User:Abhradipm and ci@lists.fedoraproject.org)
Line 28: Line 28:
  
 
* Modules and packages will be able to opt into gating.
 
* Modules and packages will be able to opt into gating.
 +
* [[FedoraAtomicCI/gating|Proposals and options]]
 
* '''Ready: August 2017'''
 
* '''Ready: August 2017'''
  

Revision as of 16:57, 18 June 2017

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.

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:

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.

Testing pipeline

The pipeline is described here.