This document describes in detail the contents of this repository. It is still a work in progress, but do not hesitate to report if something is missing.
The repository contains a set of tools to aid in the process of building, testing and releasing (open)SUSE based distributions. The Tools section enumerates and describes all these tools, including links to documentation, source code and some information about where they are used.
Apart from these tools, the repository includes:
osclib package.Most of these tools are available as packages for several distributions. Check the spec file in this repository or the devel project for further information.
For the time being, we have classified them into three different groups: command line tools, OBS bots and osc plugins. Bear in mind that the information in the following list might be wrong and incomplete.
Usually, the executables are renamed as osrt-NAME (e.g., osrt-announcer).
Generates email diffs summaries to announce product releases.
Generates and updates OBS products for openSUSE and SLE. It generates package lists based on
000package-groups and puts them in 000product (resulting kiwi files) and 000release-packages
(release package spec files).
Clean old containers from a given project like openSUSE:Containers:Tumbleweed. Only those containers providing binaries to the latest five versions for each architecture are kept.
Generates insightful metrics from relevant OBS and annotation data, based on InfluxDB and Grafana. See https://metrics.opensuse.org/.
Ingests download.opensuse.org Apache access logs and generates metrics. It is composed of a PHP
script and a set of systemd units.
Releases distribution snapshots to openQA and publishes if the result is positive.
Manages bugowner information
Manages biarch packages
Sends e-mails about packages failing to build for a long time.
Checks if all packages in a repository are newer than all other repositories.
Assists in debugging dependencies
Allows to retrieve requests from OBS with quite elaborated queries.
Scripts and templates to create staging projects.
Script to generate necessary FileProvides lines needed by OBS from repo data.
| Usage: repo2fileprovides.py primary.xml(.gz | .zst) |
Handles maintenance incident requests
Keeps track of from what project a package originates, submit updates, review requests to detect origin changes, and enforce origin specific policies like adding appropriate reviews
Assists in management of staging projects.
Makes automatic legal reviews based on the legaldb API
Checks that a submit request has correct tags specified.
Checks ABI compatibility in OBS requests.
OpenQA stuff, not sure about the details.
Inspects built RPMs from staging projects.
Checks for usual mistakes and problems in the source packages submitted by users. Used also as review bot that assigns reviews (?).
Tools for working with origin information.
Helps with OBS build cycles visualization. See the openSUSE:Factory/standard example.
Compares packages status between two projects. It determines which project has the newer version of a package, shows the diff, etc. Additionally, it is able to create a submit request from SOURCE to TARGET in case packages are different.
Manages staging projects.
The FactoryCandidates projects are used to determine whether a new package in Factory does build in the Leap version under development (see openSUSE:Leap:15.2:FactoryCandidates as example). This tool helps to manage this project by creating/updating project links for new packagers and creating SR from FactoryCandidates to the Leap project on successful builds.
Compares packages from a project against factory for differences in referenced issues and presents changes to allow whitelisting before creating Bugzilla entries. It’s used to check Factory packages have all the bug references fixed in SLE (i.e. if ‘Factory First’ policy was correctly applied).
Verifies requests for new packages have a bugowner line in the request description (used in SLE where we don’t have devel projects).