You can change the build behavior of the shared library (or pipeline or any kind of job really) by clicking "Add" in the "Additional Behaviours" subsection of the Git or GitHub SCM section and choose "Don't trigger a build on commit notifications" for pipelines or "Ignore on push notifications" in shared libraries.
In theory at least. I haven't tried that out, but the help docs looks promising. On Mon, 3 Aug 2020 at 14:04, Robert Scholte <rfscho...@apache.org> wrote: > > IIUC the issue here is that Jenkins doesn't make a difference between changed > to Global pipeline files and source repositories, so any change will directly > trigger builds of all branches of all ~100 Maven repos. > Ideally only the latter should be triggered immediately, and the first at any > random moment of the week (that's fast enough). > Just like the previous time, the Windows nodes can't process the queue fast > enough. > > Robert > > On 3-8-2020 18:47:42, Gavin McDonald <gmcdon...@apache.org> wrote: > Hi, > > Does a single configuration change always spawn thousands of builds, > building all PRs ever created? > How will future configuration changes work to prevent this from happening > again? > > Thanks > > > On Mon, Aug 3, 2020 at 2:21 PM Olivier Lamy wrote: > > > I changed a configuration to reduce maven jobs disk saving size. > > no worries builds will be absorbed quickly. > > > > On Mon, 3 Aug 2020 at 14:13, Dennis Kieselhorst wrote: > > > > > Hi, > > > > > > currently the queue is again ~3500 builds long. I already experienced > > this > > > several times. Any update on a fix? > > > > > > Best, > > > Dennis > > > > > > > > > -- > > Olivier Lamy > > http://twitter.com/olamy | http://linkedin.com/in/olamy > > > > > -- > > *Gavin McDonald* > Systems Administrator > ASF Infrastructure Team -- Matt Sicker <boa...@gmail.com>
