Details
-
Type:
Improvement
-
Status: Closed (View Workflow)
-
Priority:
Minor
-
Resolution: Fixed
-
Component/s: pipeline-maven-plugin
-
Labels:None
-
Similar Issues:
Description
Add a threshold to only trigger downstream pipelines if the generated artifact has been deployed ("mvn deploy") or if has at least been installed ("mvn install" or "mvn deploy") or if it has been at least packaged ("mvn package" or "mvn verify" or "mvn install" or "mvn deploy").
In many cases, if a generated maven artifact has just been packaged (mvn package) or installed locally (mvn install), then we don't want to trigger downstream pipelines that have a maven dependency on this generated artifact.
Solution implemented
Add a Maven Lifecycle Phase threshold to trigger downstream pipelines ("package", "install", "deploy"). By default, withMaven will only trigger if the "deploy" lifecycle phase has been reached.
Attachments
Issue Links
- is related to
-
JENKINS-46355 Add a strategy to filter which build of a multi-branch pipeline triggers downstream pipelines
-
- Closed
-
-
JENKINS-46807 withMaven should provide an option to not record a build for dependency triggering
-
- Closed
-
Code changed in jenkins
User: Cyrille Le Clerc
Path:
jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/publishers/PipelineGraphPublisher.java
http://jenkins-ci.org/commit/pipeline-maven-plugin/e431bd8a85a96f535aa00bd1ed95bbd65099737a
Log:
JENKINS-46511Option to only trigger downstream pipelines when the generated artifact has been "mvn deploy", not "mvn package" or "mvn install"