-
Bug
-
Resolution: Fixed
-
Minor
-
None
Only one downstream pipeline per parent pom dependency is triggered.
The other downstream pipelines are ignored.
+----------------+
| |
| parent-module |
| (pom file) -------------------------------------------------------------------------------+
| ---------------------------------------------+ |
+--------|---|---+ | |
| | | |
| | | |
| | +--------------------+ | |
| | | | | |
| +------------ low-level-module-1|---- | |
| | | | +-----|-----------------+ +-----|---------------+
| +--------------------+ +------ | | |
| | middle-level-module-1 ----------- top-level-module-1 |
| +--------------------+ +------ | | |
| | | | +-----------------------+ +---------------------+
+---------------- low-level-module-2 -----
| |
+--------------------+
- New snapshot created on parent-module will trigger all downstream pipelines (low-level-module-1 & 2, middle-level-module-1 and top-level-module-1
- Downstream pipeline triggers will be optimized: trigger of middle-level-module-1 and top-level-module-1 will wait for low-level-module-1 & 2 to finish
- failure on downstream pipelines will not "break the chain" (see
JENKINS-55336) and a failure of middle-level-module-1 will not prevent top-level-module-1 to be triggered (will be triggered after the failure of "middle-level-module-1" with the following message on "middle-level-module-1":[withMaven] downstreamPipelineTriggerRunListener - Triggering downstream pipeline plugins » pipeline-maven-plugin » jenkins-55336 » jenkins-55336-top-level-module » master#2 due to dependency on io.jenkins.jenkins_55336:jenkins-55336-middle-level-1:jar:2.0.8-SNAPSHOT(2.0.8-20190114.113751-7) ...
- relates to
-
JENKINS-55336 Downstream pipeline trigger - optimisation "avoid excessive trigger" should not skip some pipeline triggers in case of failure of 'intermediate' builds
-
- Closed
-