At the moment, whenever we release using Bamboo, we have to overwrite a couple of variables so that the maven tasks can communicate with SVN. These variables: -Dusername=${bamboo.user} -Dpassword=${bamboo.password} are always the same as the user currently logged into Bamboo. Can I somehow use the Bamboo credintials to automatically fill in those variables, without running a customized build?
To avoid this, can't you simply use SSH keys instead of username/passwords?
Thanks for the tips and info.
We've decided to go with a bamboo-svn user to do the builds. Tracebillity will be contained to Bamboo, not SVN as well.
How to in this link
http://mjremijan.blogspot.nl/2015/06/bamboo-maven-release-plugin-and.html
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It is not possible. All builds are run outside user context. Think about case when release is being run automatically.
Last but not least Bamboo doesn't know user's password.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We are using the username to track who changes/releases. But I will look into it, maybe we can use another technique to track it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The use SSH keys, and only push the name for tracking releases, maybe?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.