Jenkins pipeline top-level join gets triggered before sub-level join

白昼怎懂夜的黑 提交于 2019-12-11 02:31:48

问题


I've got a multi-level build pipeline with a "top-level" join (test_Join) and a "sub-level" join (test_Build1_Join) (see image below).

My test_Join job requires artifacts from both test_Build1_Join and test_Build2. I copy them by filtering on a parameter named PL_BUILD_NUMBER that's passed downstream from test_Start job. That works (see this SO post)

My problem is
Sometimes, the "top-level" join is triggered before the "sub-level" join, like in the image below. This mean that the build artifacts are not yet available and I get the following error:

Copied 1 artifact from "test_Build2" build number 33
Unable to find a build for artifact copy from: test_Build1_Join
Build step 'Copy artifacts from another project' marked build as failure
Notifying upstream projects of job completion
Finished: FAILURE

The joins are done using the "Join Trigger" plugin, with the "run post-build actions at join -> Trigger parameterized build on other projects" options.

How can I synchronise the whole pipeline better? What's the standard practice?

来源:https://stackoverflow.com/questions/26101765/jenkins-pipeline-top-level-join-gets-triggered-before-sub-level-join

易学教程内所有资源均来自网络或用户发布的内容,如有违反法律规定的内容欢迎反馈
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!