Also, how does this prevent both "every commit job" and "tagged commits"
appear as causes for a testjob build?
It will prevent testjob being triggered twice as the parameter set will be
different
i.e "every commit job" will none or default set of parameters
"tagged commits" will have an extra
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
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
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?
Probl
