Hi Josh,
what about https://wiki.jenkins-ci.org/display/JENKINS/Naginator+Plugin or
https://wiki.jenkins-ci.org/display/JENKINS/Retry+Failed+Builds+Plugin ?
Am Freitag, 29. Juni 2012 21:49:44 UTC+2 schrieb Josh D:
>
> I have a parameterized job that has a number of dependencies that it
> copies in using parametrized copy artifacts build steps, e.g.: copy:
> sim-common-linux64/SIM_COMMON_REV=${SIM_COMMON_REV}.
>
> If there isn't a build of sim-common-linux64 that matches the
> SIM_COMMON_REV, that step fails, as you would expect. What I'd like to do
> is something like:
>
> Execute copy artifacts->sim-common-linux64/SIM_COMMON_REV=${SIM_COMMON_REV}
>
> If copy fails:
> 1. Trigger parameterized build on sim-common-linux64
> 2. Re-execute copy artifacts
>
> I know I could get similar behavior by just issuing the parameterized
> build and then copying, but people here don't want to kick off jobs that
> aren't required.
>
>
