New CI/CD Runtime and Increased Build Minutes Usage

Vadym Sydorenko

Hi,

After reading your articles regarding the new CI/CD runtime, I concluded that if I want to stick to 1x/2x step sizes, I have only one option:

• Include the full IP addresses list in our network whitelist.

Otherwise, I must switch all our pipelines to 4x/8x step sizes.

However, will the switch to 4x/8x step sizes drastically increase the number of build minutes we use, and therefore require us to purchase more build minutes?

Patrik S

Hello @Vadym Sydorenko and welcome to the Community!

The size of the step dictates how many build minutes it uses. A 2x step uses twice the number of build minutes of 1x steps. In the same way, 4x steps use four times the number of build minutes of 1x steps, and so on.

As for the IP ranges, on September 17th 2024, steps using 1x and 2x will be migrated to the new runtime. If you're accessing external networks that are protected by IP allowlisting from within your Pipelines, then by that date you'll need to update your firewall with the new IP address ranges as listed in the following documentation:

• Valid IP addresses for Bitbucket Pipelines build environments 

Those are the IP ranges from the AWS environment where Atlassian Cloud Infrastructure is executed, including the Pipelines. You can filter that JSON by the regions us-east-1 and us-west-2 , and EC2 service : 

curl https://ip-ranges.amazonaws.com/ip-ranges.json | jq -r '.prefixes[] | select(.region=="us-east-1" or .region=="us-west-2") | select(.service=="EC2") | .ip_prefix' 

However, if you prefer to use the smaller set of atlassian-ip-ranges , those will only be available to 4x and 8x steps starting on September 17th. It's important to note that you only have to add this configuration for steps that must use the restricted IP range, so it's not necessarily all of your steps.

I hope that information helps! Should you have any questions, feel free to ask.

Thank you, @Vadym Sydorenko !

Patrik S