I've just started evaluating Stash and Bamboo, as a replacement for a current Git (with Gitosis) and Jenkins setup.
From reading the documentation, etc. it seems that Bamboo requires path to the Git repo, plus a username and an SSH public key to be uploaded for every build plan that's created. With the existing Jenkins setup, we only need to specify the path to the repository, because Jenkins stores an SSH key for a Gitosis user which has access to all repositories. All projects are private and ideally we don't want individual developers (whoever sets up a new Bamboo plan) to have to use their personal user account and SSH key to clone from Git.
Is there any way to achieve the same thing in Bamboo? Either creating a 'bamboo' user in Stash and somehow storing their SSH public key on the Bamboo server (so it doesn't have to be uploaded for each new plan), or making all Stash repositories publically accessible only to Bamboo?
Many thanks in advance!
If you are on Bamboo 5.2, you can use 'Shared credentials' feature.
In Administration -> Shared credentials you can define an SSH key. This SSH key will be available as authentication option when configuring Git repositories in Bamboo.
Hi Community! I’m Elaine, Confluence Product Manager. You may have read my earlier post about page tree in space navigation sidebar. I'm excited to share another improvement that helps you organize ...
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