Re: Same build, different parameters queueing for same Slave

[cjo]

Is this the same job being started with two sets of different parameters?

If so check that you have Allow Concurrent builds enabled (under advanced 
options I think).
If this is not enabled only one build of that job can run at one time 
regardless of the times triggered.

Chris



On Tuesday, November 20, 2012 2:54:17 PM UTC, Jason Swager wrote:
>
> This is what Slave Labels and the job option "Restrict where this project 
> can be run" are meant for.  Set a specific label(s) to the slaves meant to 
> run the job, then restrict the job to just that label(s).  Jenkins will 
> handle the rest.  Our own Jenkins strategy relies heavily on this feature; 
> we have pools of machines that can can the job and Jenkins distributes as 
> necessary.
>
> On Tuesday, November 20, 2012 3:10:21 AM UTC-8, Ronan Mulvaney wrote:
>>
>> Hi,
>>  
>> I have a build that we kick off with different parameters that I want to 
>> utilise against all my available slaves i.e. when one is building, the next 
>> queued build starts on another available slave.
>> Instead this queues on the same build that the first build kicks off on.
>>  
>> The build is a number of hours long so this is very inefficient and 
>> doesn't match the topology that I was hoping to achieve with Jenkins.
>>  
>> Would anyone happen to know how I can change this or if this is possible 
>> to achieve.
>>  
>> Thanks,
>>  
>> Ronan
>>
>

Re: Same build, different parameters queueing for same Slave

[Jason Swager]

This is what Slave Labels and the job option "Restrict where this project 
can be run" are meant for.  Set a specific label(s) to the slaves meant to 
run the job, then restrict the job to just that label(s).  Jenkins will 
handle the rest.  Our own Jenkins strategy relies heavily on this feature; 
we have pools of machines that can can the job and Jenkins distributes as 
necessary.

On Tuesday, November 20, 2012 3:10:21 AM UTC-8, Ronan Mulvaney wrote:
>
> Hi,
>  
> I have a build that we kick off with different parameters that I want to 
> utilise against all my available slaves i.e. when one is building, the next 
> queued build starts on another available slave.
> Instead this queues on the same build that the first build kicks off on.
>  
> The build is a number of hours long so this is very inefficient and 
> doesn't match the topology that I was hoping to achieve with Jenkins.
>  
> Would anyone happen to know how I can change this or if this is possible 
> to achieve.
>  
> Thanks,
>  
> Ronan
>

Re: Same build, different parameters queueing for same Slave

[Ronan Mulvaney]

Have tried using Labels applied to my slaves and the build restricted to 
run on the Label but this also doesn't seem to make any difference.

Same build, different parameters queueing for same Slave

[Ronan Mulvaney]

Hi,
 
I have a build that we kick off with different parameters that I want to 
utilise against all my available slaves i.e. when one is building, the next 
queued build starts on another available slave.
Instead this queues on the same build that the first build kicks off on.
 
The build is a number of hours long so this is very inefficient and doesn't 
match the topology that I was hoping to achieve with Jenkins.
 
Would anyone happen to know how I can change this or if this is possible to 
achieve.
 
Thanks,
 
Ronan