nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Using Crowd user/pw in a Bamboo variable

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?

Accepted answers

Jonas Andersson

To avoid this, can't you simply use SSH keys instead of username/passwords?

All comments

Jonas Andersson

To avoid this, can't you simply use SSH keys instead of username/passwords?

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.

Jonas Andersson

The use SSH keys, and only push the name for tracking releases, maybe?

Krystian Brazulewicz

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.

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

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

bamboo