Oh, one other constraint. Job B is parameterized and will need to get a parameter from job A. That's why I don't think something like the BuildResultTrigger plugin (https://wiki.jenkins-ci.org/display/JENKINS/BuildResultTrigger+Plugin) will work.
On Friday, April 19, 2013 11:47:07 AM UTC-4, Jerry wrote: > > I would like to guarantee that job B runs after job A terminates, for > whatever reason (including timeout, manual cancellation of the job, etc.). > > I could use the Build Flow plugin to do this by creating a flow that runs > job A and then job B, but there are actually going to be many "job A"s. > Thus I would need one flow job for each "job A" (I believe). The downside > to this is, I hope to make it easy for developers to set up their own jobs > that guarantee job B is run, and I can't rely on them always creating a > flow job. > > Another idea, which my co-worker had, is to set up some sort of external > monitoring in a script that runs outside of Jenkins. That's a lot of > complexity, though. > > I wonder if there is a plugin that just allows me to check a box like > "Guarantee post-build action" and then fill in the name of the job. It > seems unlikely that this would work even if job A is terminated, though. > > Any creative ideas? > > Thanks, > -- Jerry > > > -- 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.
