Hi there, I believe "Throttle concurrent builds" plugin should work, in fact, it's exactly what I don in roder to run different builds. Have you tried with the below setup?
<https://lh3.googleusercontent.com/-MSG_uEhaDag/VgkUE4BWydI/AAAAAAAAAmk/Au4lcjMg9tg/s1600/Screenshot%2Bat%2BSep%2B28%2B12-19-07.png> I'm based on: - Jenkins ver. 1.599 - throttle-concurrents ver. 1.8.3 I hope it helps Cheers On Monday, 28 September 2015 09:35:14 UTC+2, [email protected] wrote: > > Hi Jenkins Users, > > I am using *Jenkins 1.609* > > I have a requirement wherein > > *1) no two jobs can execute simultaneously on the same node but 2) they > can execute simultaneously when triggered on different nodes.* > No of executors configured on all slave nodes is 1. > > Default Jenkins behavior: > If job A and job B, both are triggered on same node then Job B goes in > executor starvation state because build is waiting for "too long" compared > to the time it takes to execute it. Once job B goes in this state, it gets > stuck and is not picked up for building. > > Have tried using "Exclusion plugin". It helps in achieving first point but > not the second one. > Also, have tried using Throttle concurrent builds plugin but still Job B > goes into executor starvation state. > > Is there any way wherein I can achieve both the points i.e. prevent > running the jobs simultaneously on same node but can run on different nodes > and without the second job going into executor starvation state as I cannot > change the sequence of the jobs?? > > Thanks in advance! > > > -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/d1684b31-8673-48c8-9a86-233b9ed8b3e6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
