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

Poll SCM and Timer triggers include "Changes" for a Pipeline for any/all Shared Libraries

    • Pipeline - July/August

      I noticed this while filing another ticket (JENKINS-41496), but the "Changes" view for the Pipeline run for this project "azure" has the "wrong commits" shown. See the screenshots for more.

      What basically appears to be happening is that any change to a Shared Library will result in newly triggered Pipelines which have "Poll SCM" configured. Pipelines which configure a timer will also have Changes from the Shared Library listed when it executes again.

      I think listing the Shared Library commits in "Changes" is acceptable, but triggering based on an SCM Poll for a Pipeline is very confusing behavior and IMHO incorrect behavior.

      As a shared tooling team, I would not expect my Shared Library changes to trigger a bunch of Pipelines for projects depending on them.

          [JENKINS-41497] Poll SCM and Timer triggers include "Changes" for a Pipeline for any/all Shared Libraries

          R. Tyler Croy created issue -
          R. Tyler Croy made changes -
          Attachment New: classic-changes-view.png [ 35641 ]
          Component/s New: pipeline [ 21692 ]
          Component/s Original: blueocean-plugin [ 21481 ]
          Description Original: I noticed this while filing another ticket (JENKINS-41496), but the "Changes" view for the Pipeline run for this project "azure" has the **wrong commits** shown. See the screenshots for more.

          I'm not sure why.
          New: I noticed this while filing another ticket (JENKINS-41496), but the "Changes" view for the Pipeline run for this project "azure" has the "wrong commits" shown. See the screenshots for more.


          What basically appears to be happening is that any change to a Shared Library will result in _newly_ triggered Pipelines which have "Poll SCM" configured. Pipelines which configure a timer will also have Changes from the Shared Library listed when it executes again.


          I think *listing* the Shared Library commits in "Changes" is acceptable, but *triggering* based on an SCM Poll for a Pipeline is very confusing behavior and IMHO incorrect behavior.

          As a shared tooling team, I would not expect my Shared Library changes to trigger a bunch of Pipelines for projects depending on them.
          Priority Original: Major [ 3 ] New: Minor [ 4 ]
          Summary Original: Blue Ocean "Changes" for a Pipeline are from the completely wrong repository New: Poll SCM and Timer triggers include "Changes" for a Pipeline for any/all Shared Libraries
          Andrew Bayer made changes -
          Component/s New: workflow-cps-global-lib-plugin [ 21714 ]
          Component/s New: workflow-job-plugin [ 21716 ]
          Component/s New: workflow-scm-step-plugin [ 21717 ]
          Component/s Original: pipeline [ 21692 ]
          Jesse Glick made changes -
          Component/s Original: workflow-job-plugin [ 21716 ]
          Component/s Original: workflow-scm-step-plugin [ 21717 ]
          Issue Type Original: Bug [ 1 ] New: Improvement [ 4 ]
          Jesse Glick made changes -
          Link New: This issue is duplicated by JENKINS-41442 [ JENKINS-41442 ]
          Jesse Glick made changes -
          Link New: This issue is duplicated by JENKINS-39615 [ JENKINS-39615 ]
          Jesse Glick made changes -
          Link New: This issue is duplicated by JENKINS-39499 [ JENKINS-39499 ]
          Jesse Glick made changes -
          Link New: This issue relates to JENKINS-42320 [ JENKINS-42320 ]
          Jesse Glick made changes -
          Link New: This issue relates to JENKINS-38659 [ JENKINS-38659 ]
          James Hogarth made changes -
          Issue Type Original: Improvement [ 4 ] New: Bug [ 1 ]
          James Hogarth made changes -
          Issue Type Original: Bug [ 1 ] New: Improvement [ 4 ]

            Unassigned Unassigned
            rtyler R. Tyler Croy
            Votes:
            91 Vote for this issue
            Watchers:
            98 Start watching this issue

              Created:
              Updated: