Bitbucket Branch Source Plugin - trigger build on PR when merge branch is updated

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Bitbucket Branch Source Plugin - trigger build on PR when merge branch is updated

Matthew Ceroni
I am using the Bitbucket Branch Source Plugin (https://wiki.jenkins.io/display/JENKINS/Bitbucket+Branch+Source+Plugin). Branches and PR are triggering builds when commits are pushed. However, what doesn't happen is when the merge branch of a PR is updated, the PR doesn't trigger a build. Shouldn't this be possible? (ex: FEATURE_BRANCH -> MASTER and master gets updated, say from a merge of a different PR). 

The build of the current open PR should re-run to ensure whatever was introduced into master doesn't break the code in the branch.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/44437abe-c537-47cb-9568-3f07c9ade518%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Bitbucket Branch Source Plugin - trigger build on PR when merge branch is updated

stephenconnolly

On Sun 14 Jan 2018 at 07:10, Matthew Ceroni <[hidden email]> wrote:
I am using the Bitbucket Branch Source Plugin (https://wiki.jenkins.io/display/JENKINS/Bitbucket+Branch+Source+Plugin). Branches and PR are triggering builds when commits are pushed. However, what doesn't happen is when the merge branch of a PR is updated, the PR doesn't trigger a build. Shouldn't this be possible? (ex: FEATURE_BRANCH -> MASTER and master gets updated, say from a merge of a different PR). 

The build of the current open PR should re-run to ensure whatever was introduced into master doesn't break the code in the branch.

Currently branch-api doesn’t have a special case to reconsider the effect of events on other heads.

This was in part because it would result in unwanted build storms for users that don’t want the behaviour.

Now that there are branch build strategies that can make the corresponding decision we can consider the change but it may require some tweaks in scm-api first in order to prevent excessive rate limit consumption.

Currently on a full scan, the PRs will be rebuilt (unless you install the basic branch build strategies plugin and configure PRs not to rebuild for target branch only changes)

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/44437abe-c537-47cb-9568-3f07c9ade518%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
Sent from my phone

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CA%2BnPnMzNoAdZQ82pXMaExMU8UM-U2iLY-yi4oYQLG4fa4F1TUQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.