Bitbucket Pipelines has officially launched the Runners Autoscaler feature out of beta, enabling teams to dynamically adjust CI/CD runner counts on Kubernetes infrastructure. Additionally, Bitbucket has expanded support for self-hosted runners on macOS and non-containerized Linux environments, enhancing flexibility and cost control for development teams.
- Runners Autoscaler moves from beta to general availability
- Support for macOS and non-containerized Linux self-hosted runners released
- Self-hosted runners on customer infrastructure reduce build minute costs
What happened
Bitbucket Pipelines has transitioned its Runners Autoscaler from beta to general availability, delivering automatic scaling of self-hosted runners deployed on Kubernetes. This feature adjusts the number of active runners in real-time based on the pipeline workload, improving resource efficiency and productivity.
In addition, Bitbucket Pipelines released official support for macOS self-hosted runners and non-containerized Linux Shell runners, both previously in beta. These runners run on the user’s own infrastructure, enabling builds for macOS, iOS, and Linux environments without container restrictions or additional Bitbucket build minute charges.
Why it matters
Automating runner scale helps teams optimize computing resources and cost by ensuring runner availability matches actual demand. This avoids the overhead of maintaining unnecessarily high runner counts while preserving speed and throughput for continuous integration and delivery pipelines.
The extended support for macOS and Linux self-hosted runners gives teams greater control over their build environments, enabling specialized workflows such as iOS app development and allowing use of legacy or unique infrastructure setups. This flexibility can reduce dependency on cloud-hosted build minutes and associated costs.
What to watch next
Teams using Bitbucket Pipelines should explore the autoscaling feature to tailor pipeline runner capacity dynamically and follow Atlassian’s documentation for configuration guidance. Evaluating cost and performance impacts will be important as usage scales.
Continued enhancements to self-hosted runner capabilities may include support for additional operating systems, plugins, and deeper integrations with Kubernetes and other infrastructure platforms. Monitoring user feedback will be key to anticipating future updates and feature expansions.