On Wed, Nov 24, 2021 at 2:36 PM Damien Duportal <[email protected]> wrote:
> the setting "Ignore rebuilding merge branches when only the target branch > changed" had been applied… > That probably suffices as a workaround (I have not tried this plugin <https://github.com/jenkinsci/basic-branch-build-strategies-plugin/blob/master/docs/user.adoc#change-requests> myself). FWIW my standard recommendation is to simply switch the *Strategy* for PR builds from *Merging the pull request with the current target branch revision* to *The current pull request revision*. There is not much point in using the PR-merge strategy if you are not doing fresh builds when the target branch moves, under the assumption PRs are usually based on the target branch head in effect at the time the PR was filed and that pushes of follow-up commits also include merges of the target branch as needed, since you are no longer reliably verifying that PR tests pass against the current target branch head before merging; and the PR-merge strategy has downsides other than performance, such as preventing Incrementals deployment when an actual merge is being built, and preventing lightweight (API-based) checkout of `Jenkinsfile`. The PR-head strategy is simpler to understand, and does not require a special plugin to avoid overhead. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1x2d1SpGr%3D5oeEwhN1np%2B-0J%3DwdHfSVHYB06jQsV-81A%40mail.gmail.com.
