Thanks for pointers. I'll check both the core's concepts of resources and their use in the locks/latches plugin.
Thanks again, Andy On Thursday, 31 October 2013 15:53:27 UTC, Ricardo Silva wrote: > > I've never used it myself, and maybe it uses the same concept Stephen > mentioned (so it could be broken), but the Throttle Concurrent Build > plugin [1] has a "Multi-Project Throttle Categories" which I think fits > with what you want to do. > > Declare in the global configuration a licenses category and the maximum > number, and tag all jobs that use a license with that category. (It just > doesn't fit well with jobs that use multiple licenses of a single > product.) > > [1] > > https://wiki.jenkins-ci.org/display/JENKINS/Throttle+Concurrent+Builds+Plugin > > > On 10/31/2013 04:42 PM, Stephen Connolly wrote: > > There is a concept of a Resource within Jenkins and jobs can be marked > as > > using N of that number of the Resource instances, and you can declare > how > > many total instances of the resource exist. > > > > Jenkins will stall builds until they can get the required number of > those > > resources. > > > > The locks and latches plugin uses this with resources of size 1 to > > implement locks... Beware there are bugs in the Resource model that to > my > > knowledge have never been fixed (these are mostly seen as "bugs in locks > > and latches" but actually are issues in core) have a look at the issues > in > > the locks and latches plugin to see if they are things you can live with > > before you start down that road though > > > > > > > -- > Ricardo > -- 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]. For more options, visit https://groups.google.com/groups/opt_out.
