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

XMLWordPrintable

    • 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.

        1. blueocean-changes.png
          119 kB
          R. Tyler Croy
        2. classic-changes-view.png
          39 kB
          R. Tyler Croy
        3. global-pipeline-configuration.png
          84 kB
          Giorgio Sironi
        4. image-2019-04-08-13-45-36-893.png
          10 kB
          Harrison Kim
        5. image-2023-03-21-08-38-51-401.png
          21 kB
          Bruce Coveny
        6. triggered-build-log.png
          154 kB
          Giorgio Sironi
        7. unrelated-repo-changes.png
          67 kB
          R. Tyler Croy

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

              Created:
              Updated: