-
Suggestion
-
Resolution: Done
-
Linux, Subversion
The new branch functionality shows great promise. But, and there's always a but, it doesn't handle plans with multiple source repositories.
For an example setup, I have code stored in the following svn locations:
/svn/libraries/core/trunk
/svn/libraries/widget-creator/trunk
/svn/applications/magic-8-ball/trunk
To create a clean build of the magic-8-ball application, I need to check out all three in order and build them. If I want to branch the magic-8-ball application for release and have it depend on specific versions of its libraries, the source directories might be:
/svn/libraries/core/branches/3.14
/svn/libraries/widget-creator/branches/12345
/svn/applications/magic-8-ball/branches/1.2
From a functional perspective, each of the source repositories in a plan needs to be able to have a separate source repository path when building a given branch. This path for the default build, this other path when building the '1.2' branch etc.
On the UI side when configuring a Bamboo Branch, the current location for specifying a different source repository when building for a branch is partially non-intuitive. To my mind, especially if Bamboo's concept of Branch builds becomes more central to Bamboo's operation, having the different source repositories for Branches as additional options in the Configuration -> Source Repositories -> Edit Source Repository tab would make more sense. For Branch (pulldown) use [this] repository information with [x] same password or different password etc. I really like the idea of not having to retype the same repository password multiple times.
- duplicates
-
BAM-13995 Plan branch should be able to override multiple source repositories
- Closed
- followed by
-
BAM-19898 Plans braches using multiple repositories could automatically checkout them using the same source branch name
- Gathering Interest
- incorporates
-
BAM-18527 Do not run Change Detection after customized run
- Closed
- is duplicated by
-
BAM-14875 Be able to assign branches on multiple repositories
- Closed
-
BAM-15062 Automatic branching from multiple repos
- Closed
-
BAM-12880 Being able to clone multiple separate repositories to the same branch in the same job
- Closed
-
BAM-13995 Plan branch should be able to override multiple source repositories
- Closed
-
BAM-15963 Specify secondary repository at build plan branch level instead of build plan level
- Closed
- is related to
-
BAM-11660 Autogenerated Branch-specific variables
- Closed
- relates to
-
BAM-11662 Default repository should expose its branch name as a variable
- Closed
-
BAM-11803 Provide flexibility in choosing a repository while branching a plan
- Closed
-
BAM-19854 Create plan branches for all repositories defined in a plan
- Gathering Interest
- was cloned as
-
BAM-19873 Rest API Method for branching with multiple source repositories
- Closed
- links to
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...