From Fedora Project Wiki

< CI

(List pipeline testing triggers)
(Migrated to the new Fedora docs site)
 
(10 intermediate revisions by 2 users not shown)
Line 1: Line 1:
The testing '''Pipeline''' detects tests for enabled
Moved to: https://docs.fedoraproject.org/en-US/ci/pipeline/
packages, executes the test coverage and gathers the results.
 
= Instances =
 
There are several CI pipelines enabled in the CentoOS Jenkins:
 
* [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)
 
= Links =
 
To learn more about the pipeline visit following links:
 
* [https://github.com/CentOS-PaaS-SIG/ci-pipeline/blob/master/README.md#ci-pipeline-architecture-and-design CI Pipeline Architecture and Design]
* [[FedoraAtomicCI/pipeline|Detailed pipeline description]]
* [[FedoraAtomicCI/KojiBuilds|Build options and ideas]]
* [[FedoraAtomicCI/upstream|Upstream open-source project integration]]
* [[Fedora requirements for CI and CD]]
* [https://jenkins-continuous-infra.apps.ci.centos.org/ CI-Pipeline instance in Centos CI]
 
= Examples =
 
Testing results appear as green or red dots directly in the Pagure
interface. Clicking on them will bring you to result details.
 
* [https://src.fedoraproject.org/rpms/passwd/commits/f27 passwd]
 
[[File:Pipeline-results.png]]

Latest revision as of 15:51, 18 March 2019