Thanks, Kevin.  I didn't know about that one.  Checking it out now!

On Jan 23, 2014, at 2:11 PM, Kevin Fleming (BLOOMBERG/ 731 LEXIN) 
<[email protected]> wrote:

> This problem can be solved simply with the Exclusion plugin.
> 
> ----- Original Message -----
> From: [email protected]
> To: [email protected]
> At: Jan 23 2014 12:11:25
> MachineA is not a Jenkins slave but rather my test target (I test specific 
> software on a specific hardware platform).
> 
> Or, I’ve misunderstood your question. I have only a single Jenkins instance 
> with several executors.
> 
> Thank you.
> 
> On Jan 23, 2014, at 10:18 AM, [email protected] wrote:
> 
> > Does having only one 1 executor on MachineA address your use case?
> > 
> >> -----Original Message-----
> >> From: silver [mailto:[email protected]]
> >> Sent: 23 January 2014 15:05
> >> To: [email protected]
> >> Subject: Re: blocked jobs
> >> 
> >> Does anyone have any ideas on this one?
> >> 
> >> Thanks.
> >> 
> >> On Jan 22, 2014, at 9:33 AM, silver <[email protected]> wrote:
> >> 
> >>> I like the option to block jobs if another job is running but does anyone 
> >>> have any suggestions how
> >> to extend this a bit and only block the job is parameterA is equal to X?
> >>> 
> >>> For example, I have JobA that targets MachineA and when JobA is running 
> >>> against MachineA, no other
> >> jobs can run against MachineA. So, I've listed JobA as a blocker in other 
> >> builds. However, I have
> >> other machines that could have other tests (or even the same test) run 
> >> against them but nothing will
> >> run when JobA is running.
> >>> 
> >>> I'd like to just be able to look at the parameters of the job that is 
> >>> running and only block if JobA
> >> parameterA is equal to JobB parameterA (basically, if two jobs are trying 
> >> to hit the same machine at
> >> the same time.)
> >>> 
> >>> Thanks!
> > 
> > 
> > -- 
> > This e-mail and any attachments may contain confidential, copyright and or 
> > privileged material, and are for the use of the intended addressee only. If 
> > you are not the intended addressee or an authorised recipient of the 
> > addressee please notify us of receipt by returning the e-mail and do not 
> > use, copy, retain, distribute or disclose the information in or attached to 
> > the e-mail.
> > Any opinions expressed within this e-mail are those of the individual and 
> > not necessarily of Diamond Light Source Ltd. 
> > Diamond Light Source Ltd. cannot guarantee that this e-mail or any 
> > attachments are free from viruses and we cannot accept liability for any 
> > damage which you may sustain as a result of software viruses which may be 
> > transmitted in or with the message.
> > Diamond Light Source Limited (company no. 4375679). Registered in England 
> > and Wales with its registered office at Diamond House, Harwell Science and 
> > Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
> > 
> > 
> > 
> > 
> > -- 
> > 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.
> 
> 
> -- 
> 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.

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to