Open Build Service 2.10 package build system release

Formed platform release Open Build Service 2.10, intended to organize the process of developing distributions and software products, including the preparation and maintenance of releases and updates. The system allows you to cross-compile packages for most major Linux distributions or build your own distribution based on a given package base.

Builds are supported for 21 target platforms (distributions), including CentOS, Debian, Fedora, OpenMandriva, openSUSE, SUSE Enterprise Linux, Red Hat Enterprise Linux (RHEL), and Ubuntu. Assembly is possible for 6 architectures, including i386, x86_64 and ARM. OBS covers more than 140 packages and is used as the primary build system for openSUSE, Tizen, Sailfish/Mer, NextCloud, and VideoLAN projects, as well as Linux builds for Dell, Cray, and Intel.

To build a fresh version of a given program in the form of a binary package for the desired system, it is enough to create a spec file or connect the package repository presented on the site software.opensuse.org. In addition, you can create a ready-made minimalistic environment for execution in virtualization systems, cloud environments, or for downloading as a Live distribution. When working with OBS, a developer can use a ready-made online service build.opensuse.org or establish similar system on your server. In addition, you can quickly deploy your own infrastructure using specially prepared images for virtual machines, containers, local installation or for PXE boot over the network.

It is possible to automate the download of source codes from external Git or Subversion repositories or code archives from ftp and web servers of primary projects, which eliminates the intermediate manual download of code archives to the developer's local machine and subsequent import into the openSUSE Build Service. Package maintainers are provided with the means to determine dependencies on other packages, with these dependencies automatically rebuilt when changes are made to them. When adding patches, it is possible to test them with similar packages from other projects.

You can use both the command line toolkit and the web interface to manage the Open Build Service. Tools are available to connect third party clients and use resources from external services such as GitHub, SourceForge and kde-apps.org. Developers have access to tools for creating groups and organizing collaboration. The code of all system components, including the web interface, package testing system and assembly backends, open licensed under GPLv2.

Among improvementsadded in Open Build Service 2.10:

• Completely redone a web interface that was rewritten using Bootstrap framework components, which made it possible to simplify code maintenance, unify the design of various parts and get rid of many complications (the 960 Grid System, its own theme for Jquery UI and an abundance of specific CSS were previously used). Despite the radical redesign, the developers tried to maintain the recognizability of the elements and the usual way of working to reduce discomfort when switching to a new version;
  

• Work has been done to improve support for delivery and deployment of applications for isolated containers. Prepared register to distribute containers. For example, to start a fresh environment based on the Tumbleweed repository, it is now enough to execute “docker run -ti -rm registry.opensuse.org/opensuse/tumbleweed /bin/bash”. secured
  support for tracking the state of binary assemblies (release control) in containers. Added support for kiwi profiles and the ability to generate multi-arch manifests;

• Added modules for integration with Gitlab and Page, which allow you to bind certain actions in OBS when new commits are made or when certain events occur in these systems.
• Built-in ability to upload to Amazon EC2 and Microsoft Azure cloud environments, as well as publish via Vagrant;
• sysv init scripts replaced with systemd files;
• Added support for storing metrics with performance data in the InfluxDB DBMS;
• Emoji are allowed in text fields (to be included in database.yml, you need to set the encoding to utf8mb4);
• Added option to send notifications to owners of problem reports, with information about the appearance of new comments;
• There was a function of preliminary confirmation of requests (request is accepted only after the review is completed);
• Optimized code performance for product generation and publishing in the repository. The scheduler now has the ability to incrementally update the project.

Source: opennet.ru