Details
-
Bug
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
None
-
Jenkins ver. 2.89.4, BlueOcean plug-ins 1.5.0, BitBucket branch source plug-in version 2.2.11
Description
GitHub and Bitbucket show different behavior w.r.t. re-evaluation of pull requests:
- GitHub PRs are rebuilt after their target branch is updated;
- Bitbucket PRs are not rebuilt after their target branch is updated.
I find the GitHub behavior quite useful for early detection of incompatibilities between work of multiple developers.
Although I am aware of the controversy around this behavior, I would really appreciate if Jenkins multi-branch pipelines behave in the same way for major git server vendors.
Attachments
Activity
| Field | Original Value | New Value |
|---|---|---|
| Attachment | screenshot-1.png [ 46223 ] |
viceice: is there a particular version of Jenkins or the plugin in which that option became available? I'm having this issue as well and don't see the checkbox.
Running a Multi-branch pipeline on Jenkins 2.138.2, Bitbucket Source Plugin 2.4.2 with Bitbucket Server.
Kyle Fernald
added a comment - - edited viceice : is there a particular version of Jenkins or the plugin in which that option became available? I'm having this issue as well and don't see the checkbox.
Running a Multi-branch pipeline on Jenkins 2.138.2, Bitbucket Source Plugin 2.4.2 with Bitbucket Server. kfernald I use Jenkins LTS 2.164.1 and Bitbucket Source Plugin 2.4.2 with Bitbucket Server.
Maybe the "Build strategies -> Change requests" feature is not available in your Jenkins version
viceice kfernald
That strategy might only be in: https://wiki.jenkins.io/display/JENKINS/Basic+Branch+Build+Strategies+Plugin
This is configurable:
you should simply uncheck