-
Bug
-
Resolution: Fixed
-
Blocker
-
None
-
Jenkins: 2.328
Bitbucket cloud
The new update made it so that every time a new commit is pushed to a branch, instead of a new build starting on that branch, it gets disabled.
After pressing Scan Multibranch Pipeline Now, everything returns to normal.
This error came up only after updating the plugin to 737.vdf9dc06105be and went away as soon as I downgraded to 2.9.11.
- duplicates
-
JENKINS-67502 cloudbees-bitbucket-branch-source latest version marks master branch as deleted
-
- Resolved
-
- is caused by
-
JENKINS-65909 Webhook does a scan for all refs instead only one from the payload
-
- Resolved
-
We noticed exactly the same issue this morning after also upgrading to BBBS 737.vdf9dc06105be last Friday. 'Scan Multibranch Pipeline Now' would enable the target branch for a build, but the next PR to that branch would disable the branch again. We also fixed by rolling back from 737.vdf9dc06105be to 2.9.11