On Tue, Nov 23, 2021 at 2:32 PM Damien Duportal <[email protected]> wrote:
> As part of reducing the infrastructure costs, we would like to stop > triggering builds of the pull requests on the BOM project when the target > branch is updated (as suggested in > https://issues.jenkins.io/browse/INFRA-1633 if I'm correct). > Correct. I would recommend this change be made to *all* multibranch projects on the site, but certainly heavyweight repos like `bom` are the first priority. The rationale is that each daily organization scanning triggers a bunch of > builds on this repository > No, assuming webhooks have not been lost, scanning per se should not trigger builds. Rather the problem is that a PR is merged, advancing the base branch, and then every remaining open PR is rebuilt against that new head. if an author of a pull request want their build to kick off, then they have > to update their source branch. > Yes, fine. -- 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/CANfRfr2biNek%2B%3DN5Vk3A6ySE%2BAbrDVvxJ0p81hhSUUp7Qpb7Lg%40mail.gmail.com.
