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.
-- 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/ccafb0f1-c431-43e3-8e4a-78e839a6b0a5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
