Release notes

The project is currently released as containers, versioned by release date. The latest version is tagged :latest.

XXXX-XX-XX.1

Image: registry.freedesktop.org/gfx-ci/ci-tron/gateway:XXXX-XX-XX.1 (amd64, arm64)

Nothing yet :)

2026-02-04.2: Fix for the access control script on GitLab runners on the gateway

Image: registry.freedesktop.org/gfx-ci/ci-tron/gateway:2026-02-04.2 (amd64, arm64)

This release only brings in critical bug fixes, reliability improvements, and debug options:

  • Fix the use of gateway runners on Gitlab;

  • Improve the reliability of the Gitlab ACL check in the presence of Gitlab errors;

  • Improve the resilience to unexpected owner/permissions in the config directory;

  • Add debug parameters related to Gitlab/Github job submission.

2026-02-04.1: Gitlab job prioritisation tag enforcement, distributed farms, OnePlus 6/6T

Image: registry.freedesktop.org/gfx-ci/ci-tron/gateway:2026-02-04.1 (amd64, arm64)

Bug in this release

This release contains a bug, breaking the use of the gateway runners on GitLab. Please use the next release, 2026-02-04.2, if this is a feature you need.

Breaking changes

This release starts enforcing that the jobs are correctly setting their priority tag (introduced in release 2025-11-07.1). If a job starts failing with “Priority tag is missing from the job” and you don’t care about priorities, use ci-tron:priority:default, as it’s always available, unless the project has a different policy (e.g. Mesa uses high/default/low priorities for various jobs and situations).

New contributors

  • Neil Armstrong (@narmstrong)

Highlights

The main changes found in this release are:

  • Gitlab:

    • Start enforcing that job priorities are set in every job

    • Allow setting timeouts:boot_cycle:retries value without also providing a timeout

  • Executor:

    • Allow farms to join a distributed virtual farm that can be targeted by forges jobs (FARM_ALIASES=name1,name2,... in /config/config.env)

    • Sergeant Hartman: Ability to disable training retrials

  • DUT hardware support:

    • Modernized support for the HDK8*50

    • OnePlus 6/6T (fajita/enchilada)

  • PDUs:

    • Add auto-detection for APC PDU hardware generations

  • Misc:

    • About 2x faster live deployment by making use of Ansible mitogen

    • Lots of documentation improvements

2025-12-08.1: Attached artifacts, user-configurable Wireguard tunnels, new PDU drivers

Image: registry.freedesktop.org/gfx-ci/ci-tron/gateway:2025-12-08.1 (amd64, arm64)

This release, on top of the usual fixes, brings support for attached artifacts: Artifacts that are uploaded to the gateway by the client and referenced in the job description with attached_artifact instead of url or data.

It also continues the trend of turning CI-tron into a generic project by un-hardcoding the Wireguard configuration (see /config/wireguard/wg0.conf).

Finally, this release also shines by how many new PDU drivers also landed:

2025-11-07.1: Multiplying job sources

Breaking changes

Upon rebooting on the new image, all your Gitlab runners will get removed and re-registered with an extra new tag: ci-tron:priority:$PRIORITY.

Before rebooting on the new image, please:

  • Back up /config/mars_db.yaml

  • Check that your Gitlab registration/access tokens are still valid by either asking the Gitlab instance admin to confirm your tokens are valid, or by using the following command and making sure they do not return error 401:

    curl  --header "PRIVATE-TOKEN: $token" "https://gitlab.freedesktop.org/api/v4/runners"

If any of your tokens have expired, please refer to MarsDB to see which scopes to request.

Image: registry.freedesktop.org/gfx-ci/ci-tron/gateway:2025-11-07.1 (amd64, arm64)

The main changes found in this release are:

  • Job prioritisation: Get more control over which jobs will run next

  • Initial Github support [1]

  • The dashboard v2 now replaces the original dashboard

  • It is now possible to disable exposing all runners by default on a job source, by setting expose_all_runners_by_default=false

  • Switch to Fedora 43

As you can see, this release was focused on increasing compatibility with forges while keeping the worst-case job execution latency of important jobs in check by allowing farm admins to specify the priorities of different forges/projects/users.

Finally, the new dashboard allows interacting with the new features more easily than having to edit /config/mars_db.yaml by hand.