From Fedora Project Wiki
< CI
(Instructions how to rerun tests) |
(Update pipelines) |
||
| Line 6: | Line 6: | ||
There are several CI pipelines enabled in the CentoOS Jenkins: | There are several CI pipelines enabled in the CentoOS Jenkins: | ||
* [https://jenkins-continuous-infra.apps.ci.centos.org/blue/pipelines/ Fedora] | |||
** [https://jenkins-continuous-infra.apps.ci.centos.org/blue/pipelines/?search=build-pipeline build pipeline] - non-scratch koji builds: [https://jenkins-continuous-infra.apps.ci.centos.org/blue/organizations/jenkins/fedora-f27-build-pipeline/activity/ f27], [https://jenkins-continuous-infra.apps.ci.centos.org/blue/organizations/jenkins/fedora-f28-build-pipeline/activity f28], [https://jenkins-continuous-infra.apps.ci.centos.org/blue/organizations/jenkins/fedora-rawhide-build-pipeline/activity/ rawhide] | |||
** [https://jenkins-continuous-infra.apps.ci.centos.org/blue/pipelines/?search=pr-pipeline pull-request pipeline] - tests on a pull-request: [https://jenkins-continuous-infra.apps.ci.centos.org/blue/organizations/jenkins/fedora-rawhide-pr-pipeline/activity/ rawhide] | |||
* [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) | ||
In order to manually create a new job in the pipeline (e.g. to execute the tests again because of an infrastructure error) add the following comment to the pull request: | In order to manually create a new job in the pipeline (e.g. to execute the tests again because of an infrastructure error) add the following comment to the pull request: | ||
Revision as of 11:06, 20 July 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:
- Fedora
- build pipeline - non-scratch koji builds: f27, f28, rawhide
- pull-request pipeline - tests on a pull-request: rawhide
- Atomic Host - for selected packages (trigger on commit to master)
In order to manually create a new job in the pipeline (e.g. to execute the tests again because of an infrastructure error) add the following comment to the pull request:
[citest]
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.
