Still I think this is just another flavor of the same thing and worth talking with the maintainer to find a solution. as a Jenkins developer I also tend and like to implement new stuff, but as a Jenkins User looking at the plugins page - I feel overloaded and think there is to much of the same thing to choose from... just my 5cent… up to you
On 15.08.2012, at 20:45, ThomasBrouwer <[email protected]> wrote: > The Exclusion plugin is implemented in such a way that the resource is only > obtained during certain (specified) build steps of a job. As a result, it is > impossible to put this job back into the waiting queue whilst waiting for a > resource. For my proposed plugin I intend to make it so that a job gets a > resource during its entire build, thus allowing this functionality. If I were > to extend the Exclusion plugin, I would not be able to provide this > functionality as there are cases in which both of them could be useful. I > would not mind extending the current plugin, but that would not result in the > plugin intended. > > > Op woensdag 15 augustus 2012 17:36:10 UTC+1 schreef domi het volgende: > why not integrating it into the plugin you already mentioned? > The "Exclusion Plugin" even uses the same terminology already. > …sorry, but I really think we should take more care on improving existing > plugins then just adding new ones with 80% the same functionality of an > already existing one. > Domi > > On 13.08.2012, at 11:51, ThomasBrouwer <[email protected]> wrote: > >> Hi there! >> >> I am currently planning on making a new plugin that extends the >> functionality of the Exclusion plugin >> (https://wiki.jenkins-ci.org/display/JENKINS/Exclusion-Plugin). What the >> plugin will allow you to do is to specify multiple resources of the same >> type, so that a pool of resources is created. When a job then needs that >> resource, it will be given one of them and there will be one less resource >> in the pool. This means we can specify how many jobs requiring the same type >> of resource can run (by making that many resources). When a resource is >> allocated, its name should also be passed to the job so that we know which >> of the resources was given. Also, when a resource is not available the job >> should go back into the queue, rather than waiting and taking up an >> execution slot. >> This is useful when, for example, you have multiple devices set up in a lab >> that you want a job to connect to, but there are multiple boards a job can >> use, and some it can't (because it requires a specific type of board). >> Currently we need to specify which of the boards it always runs on, but that >> is not very flexible. Sometimes a job may require multiple resources as well. >> >> Now the question is: Does Jenkins allow you to change the way it schedules >> its jobs? That seems to be the most challenging part of this plugin, and I >> got the impression some things cannot be changed. Can this? >> >> Any help is greatly appreciated! >> Thomas Brouwer >
