Hey guys. Happy Friday!

We have a build flow job that kicks off multiple jobs in sequence with a 
DSL groovy file: unit tests, creating a build, deploying, regression tests, 
etc.

Now the unit testing is a separate job that we'd like to run hourly during 
the day, while letting the main build flow job run once nightly. We've done 
this by specifying periodic builds with a cron time and that's all fine, 
good and working. :-)

The problem comes when someone wants to make a build in the *middle of the 
day* (let's say they fixed a critical bug or something). We have to 
manually disable the *hourly *unit tests so that they don't take up 
resources (slaves) or other wise interfere with the build process and it's 
annoying to turn them off and remember to turn them on again after this 
midday build. I want to block the hourly unit tests from running whenever 
the main build flow job is running, but not block the unit test job that 
runs as part of the build flow process.

What I'm trying to do is block the unit tests from running whenever the 
main build flow job is already in progress and I thought I could use the 
Block Builds plugin to do that. There is catch however. Since the main 
build flow job calls the unit test job as part of the process, it results 
in a deadlock where the unit tests are queued up until the build flow is 
finished, but the build flow can't proceed without the unit tests finishing.

*Is there a way to only queue up jobs initiated by the timer if a blocking 
job is currently executing?*

Thanks for any insight on this.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/5094668c-e515-4da9-ad9d-97004388cdb4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to