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
-
Activity
Field | Original Value | New Value |
---|---|---|
Status | Open [ 1 ] | In Progress [ 3 ] |
Attachment | image-2017-09-27-22-55-33-216.png [ 39876 ] | |
Description |
Option to only trigger downstream pipelines if the generated artifact has been deployed (mvn deploy) ant not if the generated artifact has just been packaged or installed (mvn package or mvn install). 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. |
Option to only trigger downstream pipelines if the generated artifact has been deployed (mvn deploy) ant not if the generated artifact has just been packaged or installed (mvn package or mvn install). 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. h2. 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. !image-2017-09-27-22-55-33-216.png|thumbnail! |
Link |
This issue is related to |
Link |
This issue is related to |
Summary | Option to only trigger downstream pipelines if the generated artifact has been deployed, not installed | Threshold to trigger downstream pipelines only if a Maven lifecycle phase has been executed (deploy or install or package) |
Description |
Option to only trigger downstream pipelines if the generated artifact has been deployed (mvn deploy) ant not if the generated artifact has just been packaged or installed (mvn package or mvn install). 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. h2. 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. !image-2017-09-27-22-55-33-216.png|thumbnail! |
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. h2. 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. !image-2017-09-27-22-55-33-216.png|thumbnail! |
Status | In Progress [ 3 ] | In Review [ 10005 ] |
Resolution | Fixed [ 1 ] | |
Status | In Review [ 10005 ] | Closed [ 6 ] |