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

Details

    • Pipeline - July/August

    Description

      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.

      Attachments

        Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-39615 Global Pipeline Libraries triggers the 'poll SCM' of jobs

          • Major - Major loss of function.
          • Reopened

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-39499 There is no way to set changeSet property of shared library checkout to false

          • Major - Major loss of function.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-42067 Any commit to common library SCM repository triggers all pipeline build plans

          • Major - Major loss of function.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-42320 pipeline shared library changes repeatedly trigger failing jobs

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

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-41442 Configuring Pipeline Global Library injects History into Job.

          • Trivial - Cosmetic problem like misspelt words or misaligned text.
          • Resolved

          New Feature - A new feature of the product, which has yet to be developed. JENKINS-45133 Option to remove global library changes from builds changes list

          • Major - Major loss of function.
          • Resolved
          relates to

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-38659 CpsScmFlowDefinition changelog and poll configuration

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

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-71127 "libraries" directive is not documented

          • Major - Major loss of function.
          • Open

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-65649 disable Include @Library changes in job recent changes is not respected

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

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-42320 pipeline shared library changes repeatedly trigger failing jobs

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

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-42809 Activity/Branch dashboard show pipeline library commit instead of actual built commit

          • Major - Major loss of function.
          • Closed
          links to

          Web Link PR 34

          Activity

            Descending order - Click to sort in ascending order
            debugbug Richard added a comment -

            Found the issue https://issues.jenkins.io/browse/JENKINS-71127

            debugbug Richard added a comment - Found the issue https://issues.jenkins.io/browse/JENKINS-71127
            debugbug Richard added a comment -

            No, I switched to Legacy SCM and unchecked the "Include @Library..." option.

            I have rebuilt all the projects but it still does not work and is triggered every time.

            SCM is Git(lab)

            debugbug Richard added a comment - No, I switched to Legacy SCM and unchecked the "Include @Library..." option. I have rebuilt all the projects but it still does not work and is triggered every time. SCM is Git(lab)
            bcoveny Bruce Coveny added a comment -

            debugbug - is this not solved by 'unchecking' the option for 'Include @Library changes in job recent changes' in the section 'Global Pipeline Libraries' under Manage Jenkins -> Configure?

             

            bcoveny Bruce Coveny added a comment - debugbug - is this not solved by 'unchecking' the option for 'Include @Library changes in job recent changes' in the section 'Global Pipeline Libraries' under Manage Jenkins -> Configure?  
            debugbug Richard added a comment -

            It is March 2023, five years after the bug was reported.
            I come here every time I update a global library, and Jenkins launches more than 100 projects, blocking the servers for hours.

            The fact that such a fundamental bug has not been fixed for such a long period of time frightens me every time and I think about a change of CI software.

            If it weren't for the 100+ pipelines, I wouldn't want to rewrite ....

            debugbug Richard added a comment - It is March 2023, five years after the bug was reported. I come here every time I update a global library, and Jenkins launches more than 100 projects, blocking the servers for hours. The fact that such a fundamental bug has not been fixed for such a long period of time frightens me every time and I think about a change of CI software. If it weren't for the 100+ pipelines, I wouldn't want to rewrite ....
            richmond Rich added a comment -

            gartoty, I had similar issues. Try this:

            1. Did you restart Jenkins after you made changes to the Shared Library definition ? If not, do it now.
            2. All your pipeline jobs which are getting triggered, will need reset of 'GitHub hook trigger for GITScm polling' i.e. go to each job, disable the trigger, save job, enable the trigger, save job.

            That should fix. You may try #2 on a few jobs first before doing it for all 100s of them.

            richmond Rich added a comment - gartoty , I had similar issues. Try this: Did you restart Jenkins after you made changes to the Shared Library definition ? If not, do it now. All your pipeline jobs which are getting triggered, will need reset of 'GitHub hook trigger for GITScm polling' i.e. go to each job, disable the trigger, save job, enable the trigger, save job. That should fix. You may try #2 on a few jobs first before doing it for all 100s of them.
            View 78 older comments

            People

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

              Dates

                Created:
                Updated: