docs/modules/ROOT/pages/pipeline.adoc at main

ci/docs

Petr Šplíchal e711daef6a Remove table of contents, antora changes, fix links

Page overview already provided on the right side, no need to
duplicate table of contents in individual pages. Plus added
several changes to fix local docs building. Correct links.

2022-02-16 15:08:56 +01:00

2.8 KiB

Raw Permalink Blame History

Warning

This page is outdated.

The testing Pipeline detects tests for enabled packages, executes the test coverage and gathers the results. Currently version 1.1.0 of the Standard Test Interface specification is supported.

Instances

There are several CI pipelines enabled in the CentoOS Jenkins:

They are for Fedora Rawhide, current and pending releases as reported by bodhi

Build Pipeline - non-scratch koji builds:
- Rawhide
- Other releases
Pull Request Pipeline - tests on a pull-request (both rpms and tests namespace)
- Rawhide
- List all releases
Base qcow2 images used by the pipelines:
- Rawhide
- Other releases example:
  - https://jenkins-continuous-infra.apps.ci.centos.org/job/fedora-f32-image-test/lastSuccessfulBuild/artifact/Fedora-32.qcow2

Reschedule

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:

Examples

Commit

Testing results appear as green or red dots directly in the Pagure interface. Clicking on them will bring you to result details.

passwd

Pull Request

For pull requests you can find test results in the right tab of the pull request page, for example: python-virtualenv

For re-running the tests, a comment [citest] can be added into the pull-request.

2.8 KiB Raw Permalink Blame History