From Fedora Project Wiki
< CI
(Mention tests namespace) |
(Update the list of pipelines) |
||
| Line 4: | Line 4: | ||
= Instances = | = Instances = | ||
There are several CI pipelines enabled in the CentoOS Jenkins: | There are several CI [https://jenkins-continuous-infra.apps.ci.centos.org/blue/pipelines/ pipelines] enabled in the CentoOS Jenkins: | ||
* [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-f28-build-pipeline/activity Fedora 28] | |||
** [https://jenkins-continuous-infra.apps.ci.centos.org/blue/ | ** [https://jenkins-continuous-infra.apps.ci.centos.org/blue/organizations/jenkins/fedora-f29-build-pipeline/activity Fedora 29] | ||
* [https://jenkins-continuous-infra.apps.ci.centos.org/ | ** [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 (both rpms and tests namespace) | |||
** [https://jenkins-continuous-infra.apps.ci.centos.org/blue/organizations/jenkins/fedora-f28-pr-pipeline/activity/ Fedora 28] | |||
** [https://jenkins-continuous-infra.apps.ci.centos.org/blue/organizations/jenkins/fedora-f29-pr-pipeline/activity/ Fedora 29] | |||
** [https://jenkins-continuous-infra.apps.ci.centos.org/blue/organizations/jenkins/fedora-rawhide-pr-pipeline/activity/ Rawhide] | |||
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 13:10, 22 January 2019
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 Pipeline - non-scratch koji builds:
- Pull Request Pipeline - tests on a pull-request (both rpms and tests namespace)
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
