Thanks for all the replies!
cjo's technique worked the best of the bunch so I went with that. Will have
to play around with throttle-concurrency more though... that might be
useful for another project I'm working on.
Ben
On Sun, Nov 11, 2012 at 10:59 AM, AdvanTiSS wrote:
> You can use paramete
You can use parameterized trigger plugin in conjunction with
throttle-concurrency plugin(throttle category feature).
On Saturday, November 10, 2012 3:02:30 AM UTC+2, benjamin.a.lau wrote:
>
> So I've got 2 jobs
> build
> test
>
> What I want to be able to do is make sure that they always run in
Have you enabled the "block when upstream/downstream is running" options in
the advanced section of the job config.
As this will normally keep multiple jobs in a chain, only allowing a single
job to be running at a time.
I have used these options to run a chain of 5-6 jobs run on multiple
sla
One trick I have used is to set up a separate queue for the test job and
constrain it to run only one job at a time.
You do this by creating a slave on the same machine and assign the test job to
it.
You still might need to use locks & latches if you are running the build & test
jobs in the sa
So I've got 2 jobs
build
test
What I want to be able to do is make sure that they always run in this
order and that text blocks build from running and build blocks test from
running. I was able to accomplish that using the Locks and Latches plugin.
The problem I'm running into is this...
If I sta
