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 if it errors)
build job: 'DownstreamProject/branch', propagate: false, quietPeriod: 0,
wait: false, parameters: [upstream:'${env.BUILD_NUMBER}']
Aaactually, what I'd *really* like is for a workflow build to fire an event
on completion, and have arbitary downstream (multibranch) projects
subscribe to those events.
Thus if my 'product, development' branch builds successfully, then my
downstream 'customer config, development' projects automagically trigger a
build based on these new artifacts that have become available.
I could probably lash something together in a custom plugin, but I don't
know if this is catered for in an easy way?
On Thu, Oct 29, 2015 at 9:56 PM, Andrew Bayer <andrew.ba...@gmail.com>
wrote:
> 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. And fwiw, it's all linear history for the component jobs - just
> sometimes they're run directly, sometimes they're run by the full build.
>
> A.
>
>
> On Wednesday, October 28, 2015, James Nord <jn...@cloudbees.com> wrote:
>
>> 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
>> <https://groups.google.com/d/msgid/jenkinsci-users/203abdf4-dffd-4207-acaf-e2f784e028b2%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> 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/CAPbPdOaTvsSU5NrSSZD1eTpwnGy1e%2BDi6TVODSW_grUX0ELQtg%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-users/CAPbPdOaTvsSU5NrSSZD1eTpwnGy1e%2BDi6TVODSW_grUX0ELQtg%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>
--
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/CAPYP83TwYUhWiynFCCoAh7dPUiTmJ9TgGrtV2ZhqN90MFyFq9Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
