On 2013-11-19, I wrote: > Using the Build Flow plugin, I have a master job containing a > sequence of steps invoking other, ordinary jobs. The order of the > ordinary build jobs is important, sometimes because of job > dependencies but sometimes only to avoid possible conflicts. In the > latter case, it may not be useful to perform one or more of the > master job steps if the source for the corresponding ordinary job has > not changed. Normally, using an SCM poll trigger would handle that > for the ordinary job. But when that ordinary job is called by the > Build Flow plugin, I don't see a way to skip the build. Am I missing > something? > > Using some other plugin, I think I might be able to add a pre-step > to the ordinary job to bypass the build if things haven't changed. > But then the history will show that the ordinary job did run. If it > shows the job built successfully, the absence of any build product > will be confusing (at best). If it shows the job failed, that causes > other problems. It would be much better for the master job not to > invoke the ordinary job at all in this case. > > If there is no solution available at this time, then I'd suggest > that the Build Flow plugin incorporate a way to invoke the SCM poll > method against an ordinary job. That is, instead of acting like the > "build now" command, it could ask Jenkins normal SCM checker to see > if the job needs to be built and schedule it only if that is true.
I'm surprised not to have seen any response. Is there really no solution? -- Dave Close -- 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
