#16 add page with pipeline description
Merged 5 years ago by psss. Opened 5 years ago by ph0zzy.
fedora-ci/ ph0zzy/docs pipeline  into  master

empty or binary file added
empty or binary file added
file modified
+1
@@ -1,6 +1,7 @@ 

  * xref:quick-start-guide.adoc[Quick Start Guide]

  * xref:manifesto.adoc[Manifesto]

  * xref:gating.adoc[Gating]

+ * xref:pipeline.adoc[Pipeline]

  * xref:standard-test-interface.adoc[Standard Test Interface]

  * xref:standard-test-roles.adoc[Standard Test Roles]

  * xref:examples.adoc[Examples]

@@ -0,0 +1,51 @@ 

+ :toc:

+ 

+ = Pipeline =

+ 

+ The testing *Pipeline* detects tests for enabled packages, executes the test coverage and gathers the results.

+ 

+ == Instances ==

+ 

+ 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/organizations/jenkins/fedora-f29-build-pipeline/activity[Fedora 29]

+ ** 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:

+ 

+  [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]

+ * https://fedoraproject.org/wiki/FedoraAtomicCI/pipeline[Detailed pipeline description]

+ * https://fedoraproject.org/wiki/FedoraAtomicCI/KojiBuilds[Build options and ideas]

+ * https://fedoraproject.org/wiki/FedoraAtomicCI/upstream[Upstream open-source project integration]

+ * https://fedoraproject.org/wiki/Fedora_requirements_for_CI_and_CD[Fedora requirements for CI and CD]

+ * https://jenkins-continuous-infra.apps.ci.centos.org[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.

+ 

+ * https://src.fedoraproject.org/rpms/passwd/commits/f27[passwd]

+ 

+ image::Pipeline-results.png[]

+ 

+ === Pull Request ===

+ 

+ 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]

+ 

+ image::Pipeline-pr-results.png[]

+ 

add page with pipeline description

Metadata Update from @psss:
- Request assigned

5 years ago

Looks good, merging, thanks.

Pull-Request has been merged by psss

5 years ago