Maybe you can describe more of what the end goal is, there may be another option available that people aren't thinking of because your use case isn't clear.
On Sat, Mar 31, 2018 at 7:36 AM Tim Baron <[email protected]> wrote: > Thanks for the suggestion. > > I am aware of this plugin, but as you said it is not exactly what I want: > > Each job needs to participate in the throttling voluntarily in that > plugin. What I want is a global config that limits the number of jobs > running absolutely. So no job can escape even if he likes to. > > Does somebody have a different suggestion? Or perhaps I need to discuss > the idea with the author of the throttling builds plugin. > > Tim > > -- > 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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/f4f118d9-2522-4206-8208-aab12c8b1517%40googlegroups.com > . > For more options, visit https://groups.google.com/d/optout. > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAPiUgVfd-6ThskHJUbBJvEjic0bGMCA_XFhuNTW9Y1aVBBKgCg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
