We are extending our use of Bamboo from a CI tool to a continuous deliverty tool. We have the standard 3 environments, Dev/QA, staging, and production. For security purposes we do not wish to permit production processes to communicate with DevQA directly. The Bamboo server runs in DevQA and we have remote agents running in all 3 envs. I was wondering if it might be possible to use the remote agent running in staging to proxy the connections from the remote agent in production?
Hmm, you could set up two tunnels pairs (e.g. using SSH): a pair from prod to staging and a pair from staging to QA.
The tunnel pair should forward the JMS port (default 54663) and the HTTP port under which Bamboo is visible.
But at the end this would mean that you would have some kind of access from QA to prod (on two ports), so maybe it would be easier to allow QA-prod communication between these two ports on the firewall?
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