Bamboo Triggers require an IP address update for Bitbucket Cloud
Due to recent changes on Bitbucket Outbound IP addresses, Bamboo Triggers using old IP addresses require a manual update to continue accepting Triggers from Bitbucket and run builds after Bitbucket commits.
- Making Bitbucket’s network better, faster, and ready to grow
- What are the Bitbucket Cloud IP addresses I should use to configure my corporate firewall
Following official documentation: Repository triggers the build when changes are committed (Step 2)
Update the Bitbucket Outbound IP addresses to the "Trigger IP addresses" field in the remote trigger configuration of every Bamboo plan.
- While viewing the list of plans on the Build Dashboard, click the pencil icon to the right to edit the build plan
- Click on the 'Triggers' tab and select the 'Remote trigger' from the list.
Add the Outbound IP addresses listed at What are the Bitbucket Cloud IP addresses? to the "Trigger IP addresses field":
126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52
Note: The new Outbound IP range has been broken down into 28 IP addresses due to Bamboo Triggers not allowing IP Ranges in the configuration.
- Click "Save trigger"
Bamboo will now accept requests on the new set of IPs used by Bitbucket Cloud