Koji/CBS buildsystem

CBS permissions

If you followed the needed steps to get your account and your workstation prepared with needed packages and TLS certs in place, we can proceed with basic validation.

Let's try first to confirm that we can reach CBS/koji and be authenticated (assuming that your username is user :

# cbs hello

g'day, <user>!

You are using the hub at https://cbs.centos.org/kojihub/
Authenticated via client certificate /home/<user>/.centos.cert

Now, if you're member of a SIG group (identified as sig-<groupname> , the following command should list your all your rights and you should see a corresponding build-<groupname> permission :

# cbs list-permissions --mine
build
livecd
appliance
image
build-configmanagement
livemedia

As you can see, cbs/koji is using a 1:1 relationship between FAS/ACO group membership (sig-<groupname>) and the corresponding permissions to submit tasks against specific tags (see below) associated with that SIG.

Understanding tags and targets

Koji naming convention

A build target specifies the buildroot and destination of a package for submission. That means that as a user you ask koji to build a package within a specific build environment (build target) that is using a specific buildroot to find dependencies, etc. A Tag is how koji is grouping packages all together, and built packages can be automatically added to a tag after a successfull build, or added manually between other tags with the tag-build koji task.

CBS SIGs tags structure

As you understood, each build target in CBS koji instance will have at least four tags :

• the -build one (which is where pkg is built and using the configured buildroot)
• three levels that will be used to promote packages after :
  • candidate (default tag where built packages are tagged to)
  • testing
  • release

Our koji tag structure must follow always the following structure (really for CBS, not the rule for koji but it's important for automation and release to mirror network steps) :

<SIG><CentOS_version>-<Project>-<Version>-{candidate,testing,release} , where:

• SIG : SIG name , corresponding to IPA group, without the sig- prefix (so sig-cloud would become cloud)
• CentOS Version: .el version, so 7 means CentOS 7, 8s means CentOS Stream 8, and so on
• Project : the project that the SIG want to build
• Version : project version, can be a number or a string
• repo variant: one of the following : candidate, testing or release (see Delivery about the meaning for these levels)

Let's use one example, the Cloud SIG would like to build Openstack (Yoga release) for CentOS Stream 9

The build target would be cloud9s-openstack-yoga-el9s and the tags would be : cloud9s-openstack-yoga-{candidate,testing,release}

Submit a build on CBS

Before being able to submit a build task in koji, one has to be the pkg owner for it for all possible tags, so if you want to become the "owner" of a pkg for your own SIG/group, you can proceed like this (and replace ACO_name, pkg_name and basetag with real values :

for level in candidate testing release ; do
  cbs add-pkg --owner=<ACO_name> ${<basetag>}-${level} <pkg_name>
done

Now you can submit a build task by pointing to git.centos.org URL, pointing to project to build and git commit hash (assuming that you proceeded with needed steps in the git part :

cbs build git+https://git.centos.org/rpms/<pkg_name>.git#<commit_hash>

Promoting packages to mirror network

See dedicated Delivery documentation