I still could not find a solution. But I am thinking of a workaround. Is it possible to trigger a build from a different pipeline (from a different repository) in a pipeline?
If this is possible, I could trigger the build of the root-parent pom to guarantee that every dependency is build. Am Dienstag, 11. April 2017 18:06:49 UTC+2 schrieb Jörg Wille: > > I have a multi-module maven project split in to different git repositories. > I am using a jenkinsfile with declarative syntax in each repo (in each > branch in fact) to build each maven module. The build gets triggered from > commits via webhooks in gitlab. > So far so good. Now when I commit changes to my project's API-module, I > also want to trigger builds for all other modules, which use the API as > upstream dependency. > So, the question is, (how) can I trigger downstream dependencies builds > from other repositories via pipeline? > Any maven project available using declarative pipelines, which I could use > as reference? > -- 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/9dc84a3e-9943-4e26-9688-092f180d3405%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
