From Fedora Project Wiki
< CI
(Updated current state of pipelines) |
mNo edit summary |
||
Line 8: | Line 8: | ||
* [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] | * [https://jenkins-continuous-infra.apps.ci.centos.org/view/Fedora%20All%20Packages%20Pipeline/ Fedora] | ||
** build pipeline - executes package tests for all non-scratch koji builds for all active Fedora releases and Rawhide | |||
** pull-request pipeline - 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 11:15, 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:
- Atomic Host - for selected packages (trigger on commit to master)
- Fedora
- build pipeline - executes package tests for all non-scratch koji builds for all active Fedora releases and Rawhide
- pull-request pipeline - 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:
- CI Pipeline Architecture and Design
- Detailed pipeline description
- Build options and ideas
- Upstream open-source project integration
- Fedora requirements for CI and CD
- 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.