From Fedora Project Wiki
< CI
(Add example sections) |
(Add link to the F29 pipeline) |
||
| Line 7: | Line 7: | ||
* [https://jenkins-continuous-infra.apps.ci.centos.org/blue/pipelines/ Fedora] | * [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=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-f29-build-pipeline/activity f29], [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/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) | ||
Revision as of 15:18, 4 September 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, f29, 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
Commit
Testing results appear as green or red dots directly in the Pagure interface. Clicking on them will bring you to result details.
Pull Request
For pull requests you can find test results in the right tab of the pull request page, for example: python-virtualenv
