Sign in

Build queue

Every package Solnix should build, for every architecture, and the order builders take them. Security fixes go first, then the toolchain and base system, then the maintainer's working set and the COSMIC desktop, then everything else. Within each group a package's dependencies are built before it.

loading…

Builders

The enrolled build hosts and what each did. An architecture with no builder has nobody to build it, however long its queue.

What is waiting

Queued jobs per architecture, split by the group that decides their turn. Same scale on every row.

security toolchain & base maintainer set & COSMIC everything else

How deep the dependencies go

Queued jobs by dependency depth: the number of build steps below a package. Depth 0 builds first. The green part is the maintainer set & COSMIC; the outline is everything else.

In flight now

Submissions still moving: uploading, being validated, or being published.

Next up

The next jobs a builder can take, in claim order. Most of the queue waits for a recipe or a port on that architecture, and no builder can take those yet.

    Finished, last 72 hours

    Builder jobs completed per hour (bars) and community packages published to the cache per hour (line).

    Why each job is queued