-
Suggestion
-
Resolution: Duplicate
-
None
My company currently has 34 plans configured in Bamboo.
Of these 34 plans, there are only two source repositories. One Subversion, and one CVS (we are slowly migrating to Subversion).
It would be nice if we could configure those two source repositories (including authentication credentials) once, and then in each plan we would specify a repository and a URL within that repository. An optional per-plan override for auth credentials would be a nice addition.
This would be particularly nice for us, since our IT guys insist that we change passwords every three months. We have to go through all 34 plans and change the password, one by one!
[BAM-3644] Make Source Repositories configurable separately from a build
Since this is a duplicate. I will resolve for now.
(Jake, feel free to continue commenting, perhaps on BAM-3018).
Cheers,
Edwin
Hi Jake,
Thanks for putting all the effort to raise the issue and linking it to other issues.
Whilst being able to pull out a repository would certainly be a good approach, would the ability to bulk edit a plan alleviate that pain? Of course, the bulk editing function will need to allow you to change the URL, and credentials (at a minimum).
Cheers,
Edwin
Ulrich Kuhnhardt [Atlassian]
added a comment - Hi Jake,
you can use global variables to point to a repository.
| global Variable | SANDBOX | svn://schneiderweisse/sandbox |
|---|---|---|
| Source Repository | Repository URL | ${bamboo.SANDBOX}/<your-module> |
Change the variable to point to a different repository root.
Repository authentication credentials remain on plan level.
Kind Regards,
Ulrich Kuhnhardt
Atlassian Support
Atlassian Summit - Meet our Bamboo Developers and Product Specialists
Ulrich Kuhnhardt [Atlassian]
added a comment - Hi Jake,
you can use global variables to point to a repository.
global Variable
SANDBOX
svn://schneiderweisse/sandbox
Source Repository
Repository URL
${bamboo.SANDBOX}/<your-module>
Change the variable to point to a different repository root.
Repository authentication credentials remain on plan level.
Kind Regards,
Ulrich Kuhnhardt
Atlassian Support
Atlassian Summit - Meet our Bamboo Developers and Product Specialists 
Jake Robb
added a comment - I think this is a duplicate of BAM-3018 . Sorry! 
A bulk edit would definitely alleviate most of the pain, but my instincts as a developer tell me that separating plans from repositories is the "right" approach. In an ideal world, I think Bamboo would have both!