I have a scenario where some Bamboo agents are behind a firewall and some are in front of the firewall. The Bamboo server itself sits behind the firewall.
The configured broker URI is fine for all agents behind the firewall, because they connect using the internal IP address. However the agents on the outside would need to connect to a different IP address (a gateway IP address).
How can I override the hostname which the Bamboo agent uses for connecting to the broker port 54663 on the external agents?
Changing the REST URI to the external hostname was simple (using the wrapper.conf), but of course the Bamboo agent connection hangs when trying to connect to the broker.
Any hints (besides modifying /etc/hosts on the agents)?
Changes to the wrapper.conf will only change the Bamboo baseURL.
You'll need to make sure to use an address that is both known to the internal agents and the outside agents to accomplish. If you setup port forwarding on your firewall does the traffic not reach the intended destination?
In addition, take a look at the following Community posts for more clues:
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Bamboo 5.9 will no longer be supported after June 12, 2017. What does this mean? As part of our End of Life policy, Atlassian supports major versions for two years after the first major iteratio...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs