-
Improvement
-
Resolution: Fixed
-
Minor
-
None
For downstream pipeline triggers based on snapshots, the optimisation "avoid excessive trigger" will prevent direct trigger of pipelines if they have parent pipelines that are also triggers.
+--------------+ | | | MY-FRAMEWORK | | | +-------|--|---+ +------------+ | | | | | +------- MY-LIBRARY | | | | +----------------+ | +------------+ | | | +--------- MY-APPLICATION | +-------------------------- | +----------------+
In the sample above, "my-framework" will only trigger "my-library" and NOT trigger "my-application" because "my-application" will be triggered by "my-library".
However, if an 'intermediate' build fails then the downstream pipelines that have been "skipped/omitted" never get triggered.
In the sample above, "my-application" is never triggered if the build of "my-library" fails.
"withMaven" should detect the failure of "my-library" and understand that "my-application" should be triggered.
- relates to
-
JENKINS-55566 Only one downstream pipeline per parent pom dependency is triggered
- Closed