Atlassian has officially launched the Runners Autoscaler feature for Bitbucket Pipelines, enabling teams to dynamically scale their self-hosted runners based on active build demand, improving efficiency and resource utilization.
- Runners Autoscaler efficiently scales self-hosted runners on Kubernetes
- Now supports dedicated runner groups with configurable minimum and maximum counts
- MacOS and non-container Linux self-hosted runners also officially released
What happened
Bitbucket Pipelines has promoted its Runners Autoscaler feature from beta to general availability, marking a significant upgrade in continuous integration and delivery capabilities for teams using self-hosted runners. This feature leverages Kubernetes to automatically adjust the number of active runners based on pipeline build volume, ensuring optimal utilization of resources.
Additionally, Bitbucket has extended its support to macOS and non-containerized Linux self-hosted runners, allowing organizations to run builds that require these environments without incurring additional pipeline build minute charges from Bitbucket, since runner resources are managed on their own infrastructure.
Why it matters
The availability of the Runners Autoscaler simplifies managing build infrastructure for development teams, enabling them to balance workload capacity and avoid overprovisioning or underutilization. This capability helps maintain developer productivity by ensuring sufficient runner availability during peak demand periods while preventing unnecessary idle resources.
Support for macOS and non-container Linux self-hosted runners broadens the range of build environments Bitbucket Pipelines can support, important for projects needing platform-specific builds like iOS and macOS apps. This flexibility also reduces costs tied to Bitbucket’s hosted infrastructure since builds run on customer-owned machines.
What to watch next
Users should monitor how the autoscaler impacts their CI/CD pipeline efficiency and cost savings as it adjusts runner capacity in real-time. Further improvements or integrations with other CI/CD workflows could emerge, providing more granular control or extending support to additional operating systems and environments.
Developers and teams interested in customization can explore the autoscaler’s configuration and source code available publicly, to better tailor the feature to their needs. Continued documentation enhancements and community feedback will be important for fostering adoption and addressing diverse deployment scenarios.