Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-46511

Threshold to trigger downstream pipelines only if a Maven lifecycle phase has been executed (deploy or install or package)

    Details

    • 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

            Activity

            cleclerc Cyrille Le Clerc created issue -
            cleclerc Cyrille Le Clerc made changes -
            Field Original Value New Value
            Status Open [ 1 ] In Progress [ 3 ]
            cleclerc Cyrille Le Clerc made changes -
            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!
            Attachment image-2017-09-27-22-55-33-216.png [ 39876 ]
            cleclerc Cyrille Le Clerc made changes -
            Link This issue is related to JENKINS-46807 [ JENKINS-46807 ]
            cleclerc Cyrille Le Clerc made changes -
            Link This issue is related to JENKINS-46355 [ JENKINS-46355 ]
            cleclerc Cyrille Le Clerc made changes -
            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)
            cleclerc Cyrille Le Clerc made changes -
            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!
            cleclerc Cyrille Le Clerc made changes -
            Status In Progress [ 3 ] In Review [ 10005 ]
            cleclerc Cyrille Le Clerc made changes -
            Status In Review [ 10005 ] Closed [ 6 ]
            Resolution Fixed [ 1 ]

              People

              • Assignee:
                cleclerc Cyrille Le Clerc
                Reporter:
                cleclerc Cyrille Le Clerc
              • Votes:
                1 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: