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

This issue is archived. You can view it, but you can't modify it. Learn more

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
          blueocean-changes.png
          119 kB
        2. classic-changes-view.png
          classic-changes-view.png
          39 kB
        3. global-pipeline-configuration.png
          global-pipeline-configuration.png
          84 kB
        4. image-2019-04-08-13-45-36-893.png
          image-2019-04-08-13-45-36-893.png
          10 kB
        5. image-2023-03-21-08-38-51-401.png
          image-2023-03-21-08-38-51-401.png
          21 kB
        6. triggered-build-log.png
          triggered-build-log.png
          154 kB
        7. unrelated-repo-changes.png
          unrelated-repo-changes.png
          67 kB

            Assignee:
            Unassigned
            Reporter:
            R. Tyler Croy
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Archived: