-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
0
-
1
-
Problem Definition
Currently, Bamboo allows dependent plan branches to run only under certain conditions:
- When the Parent branch name matches the Child branch name; AND
- When code is committed to the repository
References
Suggested Solution
Allow a Child branch to be triggered as a dependent Plan under the same conditions as the non-branch plans.
Workaround
There are workarounds mentioned in the article below, however, depending on your team or company policy they may not all work for you as it requires using the REST API which needs your password in a script:
Allow branch dependency to trigger when code is not committed to the repository
-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
0
-
1
-
Problem Definition
Currently, Bamboo allows dependent plan branches to run only under certain conditions:
- When the Parent branch name matches the Child branch name; AND
- When code is committed to the repository
References
Suggested Solution
Allow a Child branch to be triggered as a dependent Plan under the same conditions as the non-branch plans.
Workaround
There are workarounds mentioned in the article below, however, depending on your team or company policy they may not all work for you as it requires using the REST API which needs your password in a script: