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

Add a strategy to filter which build of a multi-branch pipeline triggers downstream pipelines

    Details

    • Similar Issues:

      Description

      Add a strategy to filter which build of a multi-branch pipeline trigger downstream pipelines.

      It's common to NOT want to trigger downstream pipelines when a PR is built.

      The downstream pipeline trigger on snapshot changes could support strategies based on the following:

      • Don't trigger downstream pipelines on PR builds or on feature branches but only on master branch and maintenance branches
        • Hard to differentiate feature branches from maintenance branches
        • If the artifact of a PR is published to a maven repo then it deserves to trigger downstream pipelines
      • Don't trigger downstream pipelines if the generated SNAPSHOT artifact has not been uploaded to a Maven repository)

      There are pros and cons, we have to find the approach that is the most consistent with other approaches in Jenkins pipeline to differentiates the behavior between branches. Declarative Pipeline is probably the most mature feature on this topic.

        Attachments

          Issue Links

            Activity

            Hide
            cleclerc Cyrille Le Clerc added a comment -

            Problem solved introducing a "threshold based on the Maven Lifecycle Phase to trigger downstream builds".

            Show
            cleclerc Cyrille Le Clerc added a comment - Problem solved introducing a "threshold based on the Maven Lifecycle Phase to trigger downstream builds".

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved: