Hello dear maintainers, 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).
The rationale is that each daily organization scanning triggers a bunch of builds on this repository, which is particularly heavy in term of resource consumption. Of course, in this setup, if an author of a pull request want their build to kick off, then they have to update their source branch. I'm writing this email since this setting as to be changed manually in the UI of ci.jenkins.io so I prefer asking: is there any voice against this change (specific to the BOM job) ? For the infra team, Damien DUPORTAL -- 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 jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/6d41557e-ea5c-4531-94fb-38a6a2629a43n%40googlegroups.com.
