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

Downstream pipeline no longer triggered

    XMLWordPrintable

Details

    Description

      This is  regression properly due to JENKINS-51680 where my downstream job depends on a maven module/artifact of the upstream snapshot

      Revert back  3.5.9 to get auto trigger working again

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-51680 Infinity Build Loop

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          New Feature - A new feature of the product, which has yet to be developed. JENKINS-51953 Better pipeline Upstream Cause with details of the Maven artifact that caused the trigger

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-53392 Support multiple artifact as cause on MavenDependencyUpstreamCause

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-53396 Verify downstream pipeline eligibility only once when multiple generated maven artifacts trigger a pipeline

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            View 27 older comments
            dantran dan tran added a comment -

            I deployed the latest from source. Upstream jobs did not come to complete after 40 minutes ( ie any ending logger about triggering).  I ended up to revert  back to 3.5.9

            The interesting is the double downstream trigger issue was there all along.  

            Thought of reverting changes at 3.5.10 where problem started?

            dantran dan tran added a comment - I deployed the latest from source. Upstream jobs did not come to complete after 40 minutes ( ie any ending logger about triggering).  I ended up to revert  back to 3.5.9 The interesting is the double downstream trigger issue was there all along.   Thought of reverting changes at 3.5.10 where problem started?
            cleclerc Cyrille Le Clerc added a comment - - edited

            there was a performance regression that was very visible in your special case with so many generated maven artifacts being dependencies on the downstream pipeline.

             Can you please test with the latest https://github.com/jenkinsci/pipeline-maven-plugin/tree/JENKINS-53396 (I have amended a commit to add a troubleshooting log message).
            1. Enable logging "org.jenkinsci.plugins.pipeline.maven.listeners.DownstreamPipelineTriggerRunListener=FINEST"
            2. Launch your upstream job
            3. You will see "299 times" in the build logs a troubleshooting message that will look like

            [withMaven - DownstreamPipelineTriggerRunListener] Skip eligibility check of pipeline dependency-graph/my-downstream-of-a-multi-jar-project/master for artifact com.example.multi-jar:jar-2:jar:0.0.1-SNAPSHOT(0.0.1-20180903.201513-17), eligibility already confirmed

            Reference: https://issues.jenkins-ci.org/browse/JENKINS-53396

            2018-09-03 22:55 CEST: code merged in master branch

            cleclerc Cyrille Le Clerc added a comment - - edited there was a performance regression that was very visible in your special case with so many generated maven artifacts being dependencies on the downstream pipeline.  Can you please test with the latest https://github.com/jenkinsci/pipeline-maven-plugin/tree/JENKINS-53396 (I have amended a commit to add a troubleshooting log message). 1. Enable logging " org.jenkinsci.plugins.pipeline.maven.listeners.DownstreamPipelineTriggerRunListener=FINEST " 2. Launch your upstream job 3. You will see "299 times" in the build logs a troubleshooting message that will look like [withMaven - DownstreamPipelineTriggerRunListener] Skip eligibility check of pipeline dependency-graph/my-downstream-of-a-multi-jar-project/master for artifact com.example.multi-jar:jar-2:jar:0.0.1-SNAPSHOT(0.0.1-20180903.201513-17), eligibility already confirmed Reference: https://issues.jenkins-ci.org/browse/JENKINS-53396 2018-09-03 22:55 CEST: code merged in master branch
            dantran dan tran added a comment - - edited

            confirm!!! installing latest from source works for me.  I can see the mentioned loggers.  Looks like we finally got the closure. The delay time is within 30sec consistently.

            Thank you.

            dantran dan tran added a comment - - edited confirm!!! installing latest from source works for me.  I can see the mentioned loggers.  Looks like we finally got the closure. The delay time is within 30sec consistently. Thank you.
            dantran dan tran added a comment -

            Tested with 3.5.12-beta-4

            dantran dan tran added a comment - Tested with 3.5.12-beta-4
            cleclerc Cyrille Le Clerc added a comment -

            3.5.12

            cleclerc Cyrille Le Clerc added a comment - 3.5.12

            People

              cleclerc Cyrille Le Clerc
              dantran dan tran
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: