On 08/02/2013 11:53, cjo wrote:
I assume that you have the jobs set up as
every commit job -> testjob
tagged commits -> testjob
Yep.
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.
Yeah, I thought of that, seem a bit of a hack though :-/
Also, how does this prevent both "every commit job" and "tagged commits"
appear as causes for a testjob build?
This can't happen, as it causes artifacts to be copied from both, which
is wrong...
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.
