Jenkins pipelines

The Jenkins testing pipelines run generic tests for Bodhi updates in Testing Farm, and gather and report the results.

Pipelines and Fedora Messaging (RabbitMQ) queues

There are several Fedora CI pipelines enabled in OSCI Jenkins. They run various tests on Bodhi updates when they are created or edited to contain different builds. The pipelines are all triggered by messages from the Fedora Messaging (RabbitMQ) system, so each pipeline has an associated message queue. This table records the active pipelines and their associated message queues, repositories and upstreams. Each pipeline must have its own queue.

Table 1. Table Queues, pipelines and repos
Queue Pipeline URL Pipeline repo Trigger repo Upstream

osci-pipelines-queue-10

Link

Link

Link

rmdepcheck dependency checker

osci-pipelines-queue-11

Link

Link

Link

Per-package TMT tests

osci-pipelines-queue-14

Link

Link

Link

installability via mini-tps

osci-pipelines-queue-15

Link

Link

Link

rpminspect package linter

osci-pipelines-queue-rmdepcheck

Link

Link

Link

rmdepcheck dependency checker

osci-pipelines-queue-scratch-build-test

Link

Link

Link

Related package scratch build test

Tests on dist-git pull requests are no longer run by Jenkins pipelines, they are handled by Packit.

Result visibility

Bodhi

Test results are found in the Bodhi web interface on the Automated Tests tab. Results whose names start with fedora-ci come from this system.

bodhi results