You could also set up slave nodes specific to these jobs and give them only one 
executor each, preventing parallel execution of jobs. I've been using this 
approach for more than two years on a number of systems for preventing parallel 
executions of tools that couldn't handle that.

On 29.07.2013, at 15:48, Andreas Ebbert-Karroum <andr...@karroum.de> wrote:

> Hi,
> 
> I am out of ideas at the moment. I am replacing a home-grown build solution, 
> that had the unique capability of only running one job at any given time. The 
> first step is to get rid of that home-grown system, changes and improvements 
> to the build process will surely follow. 
> 
> Since only one build can run at any given time, there are tools, that 
> schedule many parameterized jobs that depend on each other. To compensate for 
> that feature there are three paralell (home-grown) build servers available.
> 
> I have a problem to simulate that with jenkins. I do have parameterized jobs. 
> First I thought that I model the dependencies via up-/downstream projects and 
> just use "Block build when upstream project is building", but this has the 
> effect, that the downstream-project is built twice. First with the correct 
> parameters, triggered by the external tool. The second time, after the 
> upstream project finished.
> 
> So, another solution could be the Locks & Latches plugin, but that either 
> ends up in a) a lock that blocks each and every related job or b) a very 
> difficult lock setup (basically a lock for every library, like lock_library, 
> which is then used in every job that produces or depends on library_foo)
> 
> To end in a specific question: is it possible to block a downstream, 
> parameterized job, while the upstream job is still running, without 
> triggering a new instance of that job?
> 
> Thanks for your help,
> Andreas
> 
> -- 
> 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 jenkinsci-users+unsubscr...@googlegroups.com.
> 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 jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to