I assume that you have the jobs set up as every commit job -> testjob tagged commits -> testjob
Try adding a dummy parameter that is passed from the tagged commits job, that is unique for each build, as the ParametersAction will cause a separate builds if there are different parameters passed to ones already in the queue. This should then remove the "already in queue message". Note you don't need to use the dummy parameter, or even declare it in the test job. And as an easy way to generate the random parameter you could use the Random String parameter if you don't use the tag itself. https://wiki.jenkins-ci.org/display/JENKINS/Random+String+Parameter+Plugin Chris. On Friday, 8 February 2013 10:46:19 UTC, Chris Withers wrote: > > Hi All, > > We have a job that continuously builds our distribution. > > We also have a parameterized job that accepts a distribution from a tag, > for which we *need* to run all tests for audit/compliance reasons. > > How can I make sure this second job actually causes all downstream jobs > to run? > > Problems I've hit: > > If the downstream test job is already running, the next test job that > runs has both the continuous build and parameterized build as causes, > which means it tries to copy artifacts from both, and blows up. > > If the parameterized job is triggered twice, with two different > distributions, the second one never gets tested, as the build job for > the second build of the parameterized job says: > > "test #10 is already in the queue" > > Any help very gratefully received. > > cheers, > > Chris > > -- > Simplistix - Content Management, Batch Processing & Python Consulting > - http://www.simplistix.co.uk > -- 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.
