> > I'm working on migrating an existing build setup with a number of > individual "component" builds that both can run individually and run as > part of a "full" build >
Urgh non-linear history :-( if you separate out the logic of the individual job into a re-usable flow script that can take your parameter then your full job is not triggering the individual jobs but is one big large flow. And if you want to build the individual "component" you have a workflow just for that. Is there a way to get this same sort of behavior in workflow land? workflow jobs can be parameterized and you can trigger them with parameters. The parameters will show up as variables inside the flow script. -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/203abdf4-dffd-4207-acaf-e2f784e028b2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
