Degraded performance Customers may experience issues using Community search. Our team is investigating.
We have a Subversion repository with dozens of related projects, each with its own Maven pom.xml file. Currently the layout is:
etc. This is pretty standard and works fine with automatic branch detection in Bamboo 4.2. I can set the repository location to /project-a/trunk and it will look for branches in /project-a/branches. However, I've been considering an alternate repository layout that looks like this:
etc. This would allow us to create a branch that encompasses multiple related projects, all of which will be modified together in that branch, instead of creating separate but inter-dependent branches under each project's own trunk/branches/tags structure.
However, this structure doesn't work well with Bamboo. I can configure it to look for branches of project-a under /branches, but then it thinks /branches/<branch-name> is a branch of project-a. In reality, the branched version of project-a is one level deeper at /branches/<branch-name>/project-a.
Is there anything I can do to make automatic branch detection work on this repository setup?
(Of course, I can still add each plan branch manually.)
Old Bamboo versions assume that you have the structure that you described initially. As you see in the attachment, Bamboo version 4.2.1 allows to specify the directory where the branches will be looked for. Please let me know if that answers your question or if you have any further concerns.
Yes, I know it lets me specify the location, but as I said, I have an extra directory level between "branches" and the individual projects that Bamboo is looking for. This is because there are multiple projects within each branch. So if I tell Bamboo to manage branches for "project-a" by looking under "branches", it looks for any folder named
but it needs to be looking for folders named
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