From Fedora Project Wiki

< CI

(List pipeline testing triggers)
(Updated current state of pipelines)
Line 7: Line 7:
  
 
* [https://jenkins-continuous-infra.apps.ci.centos.org/view/CI-Pipeline/ Atomic Host] - for [https://github.com/CentOS-PaaS-SIG/ci-pipeline/blob/master/config/package_list selected] packages (trigger on commit to master)
 
* [https://jenkins-continuous-infra.apps.ci.centos.org/view/CI-Pipeline/ Atomic Host] - for [https://github.com/CentOS-PaaS-SIG/ci-pipeline/blob/master/config/package_list selected] packages (trigger on commit to master)
* [https://jenkins-continuous-infra.apps.ci.centos.org/view/Fedora%20All%20Packages%20Pipeline/ Fedora] - for all packages (trigger on commit to master, f28, f27 and f26)
+
* [https://jenkins-continuous-infra.apps.ci.centos.org/view/Fedora%20All%20Packages%20Pipeline/ Fedora]
 +
  * build pipelines - executes package tests for all non-scratch koji builds for all active Fedora releases and Rawhide
 +
  * pull-request pipelines - executes package tests on a pull-request to [https://src.fedoraproject.org/rpms packages dist-git]  to all active branches and master
  
 
= Links =
 
= Links =

Revision as of 09:53, 5 June 2018

The testing Pipeline detects tests for enabled packages, executes the test coverage and gathers the results.

Instances

There are several CI pipelines enabled in the CentoOS Jenkins:

  * build pipelines - executes package tests for all non-scratch koji builds for all active Fedora releases and Rawhide
  * pull-request pipelines - executes package tests on a pull-request to packages dist-git  to all active branches and master

Links

To learn more about the pipeline visit following links:

Examples

Testing results appear as green or red dots directly in the Pagure interface. Clicking on them will bring you to result details.

Pipeline-results.png