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

Downstream pipeline no longer triggered

XMLWordPrintable

      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

        1. pipeline-maven-plugin-1-cause-per-dependency.png
          pipeline-maven-plugin-1-cause-per-dependency.png
          474 kB

          [JENKINS-53148] Downstream pipeline no longer triggered

          dan tran created issue -
          dan tran made changes -
          Link New: This issue is related to JENKINS-51680 [ JENKINS-51680 ]
          dan tran made changes -
          Description Original: This is  regression properly due to JENKINS-51680 where my downstream job depends on a maven module/artifact of the upstream snapshot New: 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

          Cyrille Le Clerc added a comment -

          Can you enable more logs on the logger "org.jenkinsci.plugins.pipeline.maven.listeners.DownstreamPipelineTriggerRunListener", it will add more messages in the build logs.

          Can you please provide more details?

          • Style of your Maven projects
          • Relationship between the pipelines and maven projects
          • messages in the logs (particularly logs of the upstream build that is not triggering the desired downstream pipeline)

          Cyrille Le Clerc added a comment - Can you enable more logs on the logger "org.jenkinsci.plugins.pipeline.maven.listeners.DownstreamPipelineTriggerRunListener", it will add more messages in the build logs. Can you please provide more details? Style of your Maven projects Relationship between the pipelines and maven projects messages in the logs (particularly logs of the upstream build that is not triggering the desired downstream pipeline)

          dan tran added a comment - - edited

          my build consists of 3 layers. 

            * Multiple Maven pipelines in layer 1 trigger layer 2. ( maven clean deploy). This works

            * Layer 2 is one single Maven pipeline with a fairly large source tree to produce an OVA.  It also builds and maven deploys integration test code, but not running the tests

            * Layer 3 has a number of small Git repos which clone the large source tree of layer 2 on the fly and build a portion of the tree for integration test purpose ( via maven clean install ).  ie we run slow integration test suites in parallel at layer 3

           

          Layer 2 has this message:  

          [withMaven] Not triggering [x » y » z » master] because it has dependencies in the downstream project list

           

          My guess here is withMaven  thinks layer 3 has dependencies of itself already built at Layer 2

          I think I will be able to simulate this scenario with smaller pipelines, just need time

           

           

           

          dan tran added a comment - - edited my build consists of 3 layers.    * Multiple Maven pipelines in layer 1 trigger layer 2. ( maven clean deploy). This works   * Layer 2 is one single Maven pipeline with a fairly large source tree to produce an OVA.  It also builds and maven deploys integration test code, but not running the tests   * Layer 3 has a number of small Git repos which clone the large source tree of layer 2 on the fly and build a portion of the tree for integration test purpose ( via maven clean install ).  ie we run slow integration test suites in parallel at layer 3   Layer 2 has this message:   [withMaven]  Not triggering  [x » y » z » master]  because it has dependencies in the downstream project list   My guess here is withMaven  thinks layer 3 has dependencies of itself already built at Layer 2 I think I will be able to simulate this scenario with smaller pipelines, just need time      

          Cyrille Le Clerc added a comment -

          Thanks Dan, the "finer" log level granularity should display in the log if the algorithm thinks there is an infinite loop.

          Cyrille Le Clerc added a comment - Thanks Dan, the "finer" log level granularity should display in the log if the algorithm thinks there is an infinite loop.

          dan tran added a comment - - edited

          I am not able to scale down to reproduce the issue.  Ended up to install latest pipeline-maven-plugin and enable org.jenkinsci.plugins.pipeline.maven.listeners.DownstreamPipelineTriggerRunListener to finer at production build to troubleshoot

          dan tran added a comment - - edited I am not able to scale down to reproduce the issue.  Ended up to install latest pipeline-maven-plugin and enable org.jenkinsci.plugins.pipeline.maven.listeners.DownstreamPipelineTriggerRunListener to finer at production build to troubleshoot

          dan tran added a comment -

          no log.  I push the second level job and want to to see a bunch of jobs to be triggered at third level jobs.  The only message I see:

           

              onCompleted(xxxx)

           

          what kind of dependency that would produce  "Not triggering [x » y » z » master] because it has dependencies in the downstream project list" ?

          dan tran added a comment - no log.  I push the second level job and want to to see a bunch of jobs to be triggered at third level jobs.  The only message I see:       onCompleted(xxxx)   what kind of dependency that would produce  "Not triggering  [x » y » z » master]  because it has dependencies in the downstream project list" ?

          Cyrille Le Clerc added a comment -

          dantran I am preparing at the moment an improvement of this message:
          https://issues.jenkins-ci.org/browse/JENKINS-53378
          https://github.com/jenkinsci/pipeline-maven-plugin/pull/159

          Cyrille Le Clerc added a comment - dantran I am preparing at the moment an improvement of this message: https://issues.jenkins-ci.org/browse/JENKINS-53378 https://github.com/jenkinsci/pipeline-maven-plugin/pull/159

          dan tran added a comment -

          very promising, look forward with a test build of this plugin

          dan tran added a comment - very promising, look forward with a test build of this plugin

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

              Created:
              Updated:
              Resolved: