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

withMaven should provide an option to not record a build for dependency triggering

    Details

    • Similar Issues:

      Description

      In our CI we build master and maintenance branches and every pull request of each repository.

      With snapshotDependency trigger, a build on a master branch can trigger builds on PR branches. This is not wanted

      JENKINS-46511 will avoid downstream jobs coming from a PR (because we just "verify", not "deploy" a PR), but the problem will still be there on master or maintenance branches, which are "deploy"

        Attachments

          Issue Links

            Activity

            Hide
            cleclerc Cyrille Le Clerc added a comment -

            benoit guerin can you please detail more your use case? Can you provide a sample Jenkinsfile and explain what would be the branches and PRs of the applications and which you would not like to see triggering downstream jobs.

            Show
            cleclerc Cyrille Le Clerc added a comment - benoit guerin can you please detail more your use case? Can you provide a sample Jenkinsfile and explain what would be the branches and PRs of the applications and which you would not like to see triggering downstream jobs.
            Hide
            falcon benoit guerin added a comment -

            Cyrille Le Clerc sorry for being silent so long

            It seems I will close this issue, since ignoreUpstreamTriggers and skipDownstreamTriggers will help with my scenario (I misunderstood how they works)

            But I need more time to test all of this

            Show
            falcon benoit guerin added a comment - Cyrille Le Clerc sorry for being silent so long It seems I will close this issue, since  ignoreUpstreamTriggers and  skipDownstreamTriggers  will help with my scenario (I misunderstood how they works) But I need more time to test all of this
            Hide
            cleclerc Cyrille Le Clerc added a comment -

            benoit guerin can you please test pipeline-maven-3.0.1-beta-1.jar and the downstream trigger based on the Maven lifecycle threshold.

            Regarding your "maintenance branches", I don't catch why they use the same snapshot versions as the "master" branch and cause undesired triggers. Could you please detail?

            The default threshold is "deploy" which seems to meet your goals. You can change it to "package" or to "install".

            https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/pipeline-maven/3.0.1-beta-1/pipeline-maven-3.0.1-beta-1.jar

            Show
            cleclerc Cyrille Le Clerc added a comment - benoit guerin can you please test pipeline-maven-3.0.1-beta-1.jar and the downstream trigger based on the Maven lifecycle threshold. Regarding your "maintenance branches", I don't catch why they use the same snapshot versions as the "master" branch and cause undesired triggers. Could you please detail? The default threshold is "deploy" which seems to meet your goals. You can change it to "package" or to "install". https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/pipeline-maven/3.0.1-beta-1/pipeline-maven-3.0.1-beta-1.jar
            Hide
            falcon benoit guerin added a comment -

            It is all working fine. In fact, during my tests, I met JENKINS-46368

            Show
            falcon benoit guerin added a comment - It is all working fine. In fact, during my tests, I met  JENKINS-46368
            Hide
            cleclerc Cyrille Le Clerc added a comment -
            Show
            cleclerc Cyrille Le Clerc added a comment - Thanks benoit guerin

              People

              • Assignee:
                cleclerc Cyrille Le Clerc
                Reporter:
                falcon benoit guerin
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: