Problem Definition

Bitbucket Cloud IP addresses for outbound connections are subject to a non infrequent amount of IP range changes which can make managing the Remote Trigger whitelisting problematic for administrators who have a large amount of plans that require updating.

Suggested Solution

Centralized / shared location where this whitelist can be maintained would be ideal. This could be then selected on a remote trigger. Or allow global variable usage in this field.

Workaround

Option 1

Use the a Bamboo Administration >> Bulk Actions with the Replace Triggers action to replace triggers on all plans with the an updated version with the new set of IP addresses.

Option 2

Utilize Bamboo Specs and source the list from a single location/variable for all your plans.

Option 3

Allow all for the Remote Trigger whitelist and manage security / whitelisting instead at your firewall.