🚀 Announcement: Migration to Dynamic Community Runners

Technical Discussions Infrastructure
1

Hi Everyone,

We’re moving our CI infrastructure from static runners to dynamic, autoscaling runners (starting from 15th Oct 2025) for the following tags:

  • amd64

  • extra-privileged

  • arm64

  • arm64-extra-privileged

Unlike the old setup (where each tag was backed by a standalone EC2 instance), the new runners automatically scale out and scale in based on CI workload demand — improving performance and reliability.

:blue_book: More details are available here:
:backhand_index_pointing_right: Elxr Community Runners Wiki

What’s Changing

We’ll gradually decommission the old static runners and let the dynamic runners handle jobs with the same tags.

No changes are required from your side.

If you encounter any CI job failures related to runners, please reply to this topic with the CI job URL so our team can investigate.

Thanks for your support as we continue improving Elxr’s CI experience!

— Elxr DevOps Team

4 Likes
2

Update — Dynamic Runner Rollout for amd64 Tag
Hi Everyone,

As part of our migration to dynamic autoscaling runners, we’ve completed the first step of the rollout.

:white_check_mark: Dynamic runners are now enabled to pick up CI jobs tagged with amd64.
:no_entry: Static runners have been disabled for this tag to ensure jobs are handled exclusively by the new autoscaling setup.

This change is part of our gradual transition plan, and we’ll continue monitoring the job performance and stability closely.

If you notice any issues or failed jobs related to amd64 runners, please share the CI job URL in this thread so we can investigate promptly. Thanks.

— Elxr DevOps Team

3

Update — Dynamic Runner Rollout for arm64 Tag

Hi Everyone,

:white_check_mark: Dynamic runners are now enabled to pick up CI jobs tagged with arm64.
:no_entry: Static runners have been disabled for this tag to ensure jobs are handled exclusively by the new autoscaling setup.

If you notice any issues or failed jobs related to arm64 runners, please share the CI job URL in this thread so we can investigate promptly. Thanks.

— Elxr DevOps Team

4

Update — Dynamic Runner Rollout for extra-privileged and arm64-extra-privileged Tag

Hi Everyone,

:white_check_mark: Dynamic runners are now enabled to pick up CI jobs tagged with extra-privileged and arm64-extra-privileged Tag.
:no_entry: Static runners have been disabled for this tag to ensure jobs are handled exclusively by the new autoscaling setup.

If you notice any issues or failed jobs related to runners, please share the CI job URL in this thread so we can investigate promptly. Thanks.

— Elxr DevOps Team

1 Like
5

Is this what is currently causing pipelines to be stuck without any runners? Such as this - extract-source (#11758655823) · Jobs · eLxr / Tools / pasha · GitLab ? Is there changes pending to the pipeline project to get these functional again?

6

Mark, the job remained in a pending state because it didn’t have any tags assigned. The new dynamic runners don’t accept untagged CI jobs. For the extract-source job, you’ll need to assign the amd64 tag.

You can refer to the supported tags listed in the Wiki. :backhand_index_pointing_right: Elxr Community Runners Wiki

7

Is there work underway or plans to update projects to be inline with this new expectation as part of the migration to dynamic runners? This should not be left open ended.

8

I agree, Mark. For the time being, we are addressing this at the runner level to resolve the untagged CI job failures. No manual action will be required from users to fix this.

1 Like
9

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.