-
Suggestion
-
Resolution: Low Engagement
-
None
-
0
-
For automatic branch detection Bamboo assumes that a user has organized his repository this way:
/project-a/trunk /project-a/branches /project-a/tags /project-b/trunk /project-b/branches /project-b/tags
This is pretty standard and works fine with automatic branch detection in Bamboo 4.2. The user can set the repository location to /project-a/trunk, and it will look for branches in /project-a/branches. However, users have been considering an alternate repository layout that looks like this:
/trunk/project-a /trunk/project-b /branches/<branch-name>/project-a /branches/<branch-name>/project-b
This would allow him 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. The user can configure it to look for branches of project-a under /branches, but then Bamboo 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.
- mentioned in
-
![[Extranet] Page](/images/icons/generic_link_16.png "[Extranet] Page")
Page
Failed to load
[BAM-12257] Provide flexibility in choosing a repository branch path
Initial request: https://answers.atlassian.com/questions/93594/repository-layout-for-branch-detection
Hello,
Thank you for submitting this suggestion. We appreciate you taking the time to share your ideas for improving our products, as many features and functions come from valued customers such as yourself.
Atlassian is committed to enhancing the security and compliance of our Data Center products, with an emphasis on sustainable scalability and improving the product experience for both administrators and end-users. We periodically review older suggestions to ensure we're focusing on the most relevant feedback. This suggestion is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments. This inactivity suggests a low impact. Therefore, this suggestion is not in consideration for our future roadmap.
Please note the comments on this thread are not being monitored.
You can read more about our approach to highly voted suggestions here and how we prioritize what to implement here.
To learn more about our recent investments in Bamboo Data Center, please check our public roadmap.
Kind regards,
Bamboo Data Center