[workflow] How do you approach multiproject builds in workflow?

[Derek VerLee]

Hi, 

  Just wondering what the most common approach is to handling multiple projects, some of which have interdependencies?

IE, do you orchestrate with one "parent" workflow build that evokes other jobs, or do you make "one big workflow" for your whole team?

We have several projects, some of which produce deployable artifacts, shared libraries, or both.

It would be desirable to build a project and any downstream dependents (on the same branch) automatically when on a "develop" or "feature" branch,

and a slightly different process if on a "stable" or release branch.

[Andrew Bayer]

This is a really good question. The most Workflow-y way to do this would be the "one big workflow" model. My instincts, admittedly, are to break it up more so that each project can be built independently as well as part of the whole Workflow - I haven't yet found an elegant way to do that in a "one big Workflow" job, but I could be missing something. 

The tweaked behavior depending on branch...that, I feel like, should be doable in Workflow scripting, but I'm not 100% sure that the branch information is actually available there.

A.

--
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-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/ccafb0f1-c431-43e3-8e4a-78e839a6b0a5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.