-
Bug
-
Resolution: Fixed
-
Low
-
None
-
5.9.1
-
None
Problem:
Plan branches are added for disabled plans
Steps to Reproduce:
- Configure Bamboo to use a linked repository to Stash
- In Stash, pull requests to require 1 approver and 1 successful build
- Create a build plan in which the option "Automatically manage branches" is checked
- Clone this build plan
- Disable the cloned build plan.
- Make a commit on a new branch
Both build plans get branch plans created for them, even the disabled on. The build on the disabled plan fails. Stash then sees both a passing build in the original plan and a failed build in the disabled cloned plan. Now Stash will not let the merge go process as it sees the failed build in the disabled plan as not meeting the requirement to allow the pull request to be merged as Stash seems to require a passing build in all plans where the branch build might occur.
Expected Behavior:
The desired behavior is that if the overall plan is disabled, it should not allow automatic branch plans to obtain the branch unless manually added.
Workaround:
Disable all the individual branch plans or delete the disabled plan.
[BAM-16094] Branches still added when plan is disabled
What version of Bamboo was this fixed in? I just hit this problem in v7.0.6 today. Most developers and admins would expect disabling a plan to disable automatic branch creation too. It's annoying because our Bitbucket policy prevents merging code with failed builds, and BitBucket won't disregard the build result for a queued build that was manually cancelled. Now I have to wait 1h for a silly duplicated build to pass in an automatically created branch in a disabled plan!
| Workflow | Original: Bamboo Workflow 2016 v1 - Restricted [ 1442983 ] | New: JAC Bug Workflow v3 [ 3381037 ] |
| Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
If this is not a bug but intended behaviour then the intended behaviour is wrong here.
Right now I have disabled plans that keep polling a (not existing anymore) repository:
- the plan is disabled
- all triggers have been deleted
- all branches are disabled too
- the branch configuration is set to "Do not create plan branches"
But still the error logs are filling up with entries that the plan tries to poll the deleted repository for changes.
I do not want to delete the plan, it should just stop polling for changes.
This is polluting the error log and is very annoying and this behaviour should be changed.
| Workflow | Original: Bamboo Workflow 2016 v1 [ 1420725 ] | New: Bamboo Workflow 2016 v1 - Restricted [ 1442983 ] |
| Workflow | Original: Bamboo Workflow 2014 v2 [ 904246 ] | New: Bamboo Workflow 2016 v1 [ 1420725 ] |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Needs Triage [ 10030 ] | New: Resolved [ 5 ] |
| Status | Original: Open [ 1 ] | New: Needs Triage [ 10030 ] |
Can't believe it's 2025 and this is still happening 10 years later. I have a plan that was created via specs. The specs were deleted, plan was disabled (but kept for log history) and it still creates branches and runs builds. What do I have to do to kill it? Recreate the specs, reenable the specs, update the branch creation mechanism and then remove the specs again? This is dumb,