Bitbucket users must upgrade their self-hosted Pipelines runner to version 3.0.0 or later by December 2, 2024, to maintain stable functionality and benefit from significant improvements.
- Mandatory upgrade to runner 3.0.0 due by Dec 2, 2024
- Runner now communicates directly with AWS S3 requiring IP allowlist updates
- Support expanded for Linux and Windows self-hosted runners without container limits
What happened
Atlassian has released Bitbucket Pipelines runner version 3.0.0, which introduces major improvements in artifact and cache handling, boosting reliability and speed. Due to the scale of these enhancements, older runner versions will face issues, prompting Atlassian to mandate an upgrade to version 3.0.0 or later by December 2, 2024.
The update also changes how the runner communicates with storage, now directly interfacing with AWS S3. This means infrastructure using IP or URL-based allowlisting must update settings to permit traffic to specific AWS IP addresses. Documentation and change history are available to assist customers with the transition.
Why it matters
Upgrading to version 3.0.0 ensures a more secure and performant Bitbucket Pipelines experience with fewer disruptions. Users who delay or do not upgrade risk losing access to self-hosted runner functionality and missing out on ongoing product enhancements.
The direct connection between the runner and AWS S3 storage requires administrators to rethink network security configurations, potentially impacting firewall and allowlist rules to avoid build failures or access issues. This signals a shift toward cloud integration that users need to manage carefully.
What to watch next
Atlassian announced plans to implement a premium tier for runners, shifting from the current model to free and paid tiers. This migration will affect how runners are managed and billed and is detailed in upcoming communications and blog posts.
Bitbucket Pipelines has also expanded self-hosted runner support beyond containers, enabling Linux shell runners and Windows runners for .NET builds. This broader OS support offers more flexibility for teams but requires adapting to new configuration and operational practices.