Gentle bump :-)

On Monday, December 9, 2013 4:25:51 PM UTC+1, robin.jarry wrote:
>
> Yes I already looked at this plugin but with I found some limitations 
> (which I'm not sure can be worked around):
>
>    - It doesn't seem possible to schedule several builds of the same 
>    projects while allowing only 1 build at a time (only 1 build is put in the 
>    queue, the others are rejected). This is a big limitation because it 
> forces 
>    users to wait for a "free slot" to schedule their build.
>    - An implication of the first limitation is that you cannot schedule 
>    new builds with a higher lock priority over some resources (the queued 
>    builds of the Throttle plugin seem to be flagged as "non-buildable" until 
>    they are allowed to pass, this makes them "non-sortable" and therefore not 
>    seen by the QueueSorters).
>    - Our plugin has a "Lockable Resource" page which displays which 
>    builds holds the lock on which resources.
>
> Do you think that the Throttle plugin could be adapted in this direction? 
> If not, is our plugin really too redundant?
>
> Cheers,
>
> --
> Robin
>
>
> On Monday, December 9, 2013 3:57:07 PM UTC+1, Jason Swager wrote:
>>
>> Would the Throttle Plugin (
>> https://wiki.jenkins-ci.org/display/JENKINS/Throttle+Concurrent+Builds+Plugin)
>>  
>> do what you want?
>> Jason
>>
>> On Monday, December 9, 2013 6:21:17 AM UTC-8, robin.jarry wrote:
>>>
>>> Hello all,
>>>
>>> We recently began to use Jenkins to run our integration and performance 
>>> tests. The main need we have is to be able to assign test platforms to 
>>> Jenkins jobs to make sure these platforms are used by one job at a time 
>>> (and queue the jobs that need these platforms accordingly).
>>>
>>> I came across the External Resource Dispatcher 
>>> plugin<https://wiki.jenkins-ci.org/display/JENKINS/External+Resource+Dispatcher>and
>>>  tried to use it. Unfortunately it didn't respond to our need (our test 
>>> platforms are not directly tied to a Jenkins node, and we don't have any 
>>> "meta-data" to attach to the external resources).
>>>
>>> Therefore we developed a very simple plugin licensed with MIT 
>>> https://github.com/6WIND/lockable-resources-plugin and we would like to 
>>> share it with the community.
>>>
>>> Is this plugin a good candidate ?
>>>
>>> Thanks in advance,
>>> Robin
>>>
>>

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to