No way to easily turn off the wait. A couple of solutions for you to consider:
1) Modified the code in the jenkins plugins that are blocking you to not wait for previous builds to complete. 2) Instead of posting to a parameterized job, the client would create a new job and post the build there. so you will have many jobs and they will get cleaned up when finished or on a nightly basis. On Tuesday, June 25, 2013 4:05:35 PM UTC-7, Corey wrote: > > We recently consolidated 40+ build jobs on Jenkins into a single > parameterized job that supports builds on multiple branches and includes > several boolean build parameters that control which submodules will be > rebuilt before packaging everything together. Because we don't want a build > on one branch getting in the way of builds on any other branch, we checked > the "Execute concurrent builds if necessary" checkbox. This worked > wonderfully until we realized that the run time of the job can vary greatly > depending on the number of submodules that need to be rebuilt. If a > short-running job is started after a long-running one, it's Post-build > Actions will not begin until the previous long-running job has completed. I > expect this may be working as designed to support the tracking of the > stability of the job. Is there any way to turn off the checking of status > of the previous job? Or is there a better way to accomplish what we are > trying to do -- a single parameterized Jenkins job that supports multiple, > independent, branches of development? -- 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.
