System overview

AlmaLinux Build System Build Node - ALBS Node - is designed for the automated building of rpm/deb packages. It uses docker and docker-compose for local\production deployment. Build Node supports several types of architectures: x86_64, aarch64, ppc64le. The support of the architectures is provided by the packages that were built for AlmaLinux Build Node specifically.

Build Node requires this albs-* services:

• AlmaLinux Build System Web-Server (albs-web-server) - puts a new build into a queue for Build Node;
• AlmaLinux Build System Build Node (albs-node) - receives and performs a build task, sends the results as artifacts to PULP, informs web-server about results.

Build Node sends a request to the Web-Server. If there is an idle task (not started), Build Node receives back a build task to build packages. After the task is completed, Build Node uploads artifacts which are build logs and rpm/deb packages to the Artifact Storage (PULP).

Mentioned tools and libraries are required for ALBS Node to run in their current state:

• Docker
• Docker-compose

Build Node flow

Currently, it is available to build for the AlmaLinux-8 OS mentioned architectures: x86_64, aarch64, ppc64le. Also, you can build both from the project tag or branch:

• projects from git.almalinux.org
• projects from any git-reference
• projects from the third-party link on src.rpm

Build Node can manage multiple builds at the same time, max number of simultaneously is configurable value (default: 4). In case of a failed build, artifacts that appeared before the fail moment will be uploaded to the PULP.

The process:

• Prepare a specially isolated environment. For the rpm, the mock utility creates one. A Build Node receives a task from the Web-Server by requesting /api/v1/build_node/get_task, creates a mock-environment to build an rpm package, and sends artifacts to the Artifact Storage (PULP). For deb, pbuilder utility is used.
• Preparing the project source code for building. In the case of rpm, this means creating an src-rpm using a SPEC file, creating source tarball (in case it's missing from the repository), applying patches, and possibly other operations according to SPEC. In the case of deb, it is creating source tarball, applying patches, other operations according to debian/rules and packing the prepared set of source files. After that, all build artifacts are transferred (src.rpm, dsc and logs) to special directories.
• The building of binary packages in a special environment based on the prepared source code from the previous stage.
• The transfer of all build artifacts (src.rpm, dsc and logs) takes place.

Running using docker-compose

You can start the system using the Docker Compose tool.

Pre-requisites:

• docker and docker-compose tools are installed and set up;

To start the system, run the following command: docker-compose up -d. To rebuild images after your local changes, just run docker-compose up -d --build.

Reporing issues

All issues should be reported to the Build System project.