Bamboo Triggers require an IP address update for Bitbucket Cloud

Still need help?

The Atlassian Community is here for you.

Ask the community

Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.

Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Purpose

Due to 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.

Documentation:

Steps:

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.

  1. While viewing the list of plans on the Build Dashboard, click the pencil icon to the right to edit the build plan
  2. Click on the 'Triggers' tab and select the 'Remote trigger' from the list
  3. Add each Outbound CIDRs listed at IP addresses and domains for Atlassian cloud products - Outgoing Connections to the "Trigger IP addresses field". Separate each block with commas.

  4. Click "Save trigger"

Bamboo will now accept requests on the new set of IPs used by Bitbucket Cloud

Last modified on Mar 21, 2022

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.