Is it possible for workflow-multibranch jobs to take parameters?
I have a similar requirement where I'd like a 'parent' workflow job to
trigger some number of downstream child jobs, probably with something like
(despite the warning in the snippet generator, I don't care to wait for the
outcome or
Yeah, separate component jobs using the global library to replace the
"generic" jobs we've used for building packages on all the different
platforms we support, and the "full" build launching the component jobs via
workflow as well seems to be the direction that's making sense for the use
case.
>
> 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
Hey! 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. I'm using the parameterized trigger plugin for all
this - the component builds behave slightly differently depending on
whether
