One option would be the Batch Task Plugin
<https://wiki.jenkins-ci.org/display/JENKINS/Batch+Task+Plugin>. You
could also look at the Build Pipeline Plugin
<https://wiki.jenkins-ci.org/display/JENKINS/Build+Pipeline+Plugin>,
which allows manual triggering of a downstream job.
Eric
On 3/12/2013 4:10 PM, Wade C wrote:
Perhaps I'm going about this the wrong way, but we have a gerrit
monitor build job that, as the last step, creates an image for
deployment. The thing is, on this job, we're mostly using it for
build testing, and the deployment step will not fail if the build has
succeeded up to that point. The image generation step is quite
time-consuming, so we'd like to avoid it in general. We usually run a
separate job to generate QA images for deployment.
In the rare case, though, QA will want to have the image to deploy.
Is there a way to specify, for a given build that has completed, that
an extra step happen, or perhaps to trigger a linked job that runs in
the same workspace based on some paramters from the monitor job?
--
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.
--
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.
