From Fedora Project Wiki

< CI

(Include PR result example)
(Migrated to the new Fedora docs site)
 
(4 intermediate revisions by the same user 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/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)
 
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:
 
* [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]]
 
For pull requests you can find test results in the right tab of the pull request page, for example: [https://src.fedoraproject.org/rpms/python-virtualenv/pull-request/3 python-virtualenv]
 
[[File:Pipeline-pr-results.png]]

Latest revision as of 15:51, 18 March 2019