Javier Hernández Antúnez

Right now, the build scheduler is dispatching whatever gets into the system to build nodes without taking into account whether it's a community product or the AlmaLinux product. In order...

After #293 is implemented, we need to ensure that `gpgkey` field in resulting COPR repo file follows the option "requires sign", this is: * When sign is required, the COPR...

Currently, we can't release an unsigned package into a product. For community products, we'd need to allow community product owners to do so (at their own risk). * This involves...

During the release process, the `repo beholder` is used in order to determine the repo where a package is going to be placed. For this reason, we'd need to be...

Let's say that we have a product with several repositories (`stable`, `beta` and `testing`), and as a product maintainer I want to release packages into `testing` first, then into `beta`,...

In order to provide a more granular configuration and ensure that community products don't interfere with AlmaLinux building, we need to add the ability in sign nodes to only sign...

The problem in https://github.com/AlmaLinux/build-system/issues/322 was due to our inability to store a >2048 token coming from KeyCloak into db when logging in, see: ``` web_server-1 | DBAPIError: (sqlalchemy.dialects.postgresql.asyncpg.Error) : value...

As unveiled in the [following issue](https://github.com/AlmaLinux/build-system/issues/430) and resolved in [this PR](https://github.com/AlmaLinux/albs-frontend/pull/588), there might be some navigation in other places due to use of calling `next()` as part of promise handling...

We need to add monitoring to public-errata-parser, mostly: * Ensure that the process/service is running and trigger an alert when it is not * Bonus points if we can add...

We need to add monitoring for the test nodes. This involves: * Create a test node specific `Am I alive` template * Add the required items in order to trigger...