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

disable Include @Library changes in job recent changes is not respected

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      Even when I disable (un marking) the "Include @Library changes in job recent changes" option from the global configuration under Global Pipeline Libraries:

       

      From some reason I still see commit changes from my shared libraries in a different multi branch job that uses  declarative pipeline.

      sample from the multi branch job declarative pipeline:

      pipeline {
          libraries {
              lib('pipeline-library')
          }
          ...
      }

      How to reproduce:

      1. Disable the "Include @Library changes in job recent changes" under global conf
      2. create standard pipeline job and use declarative pipeline
      3. import some shared libraries like the sample above
      4. perform change in your shared libraries and push your changes by creating a new commit
      5. run your pipeline job
      6. checkout the job changes and verify that you see commits from the shared libraries which shouldn't be here

       

      I can see that this has been discussed here: 

      https://issues.jenkins.io/browse/JENKINS-39615

      and here

      https://issues.jenkins.io/browse/JENKINS-39615

      But those tickets are more talking about jobs that are triggered automatically due to changes in shared libraries. While this ticket is more about changes that should  not be presented on the job history under the commit list

        Attachments

          Issue Links

            Activity

            Hide
            mcascone Max Cascone added a comment - - edited

            I have this exact issue as well. It is very confusing for the pipeline consumers to see changes that have nothing to do with their repo in their pipeline run UIs. 

             

            There is discussion here about disabling the changelog when loading a library, but is there a way to disable the changelog for all pipelines that consume the library, in the library itself? Instead of having to go and modify all consumers?

            Show
            mcascone Max Cascone added a comment - - edited I have this exact issue as well. It is very confusing for the pipeline consumers to see changes that have nothing to do with their repo in their pipeline run UIs.    There is discussion here  about disabling the changelog when loading a library, but is there a way to disable the changelog for all pipelines that consume the library , in the library itself? Instead of having to go and modify all consumers?

              People

              Assignee:
              mjdetullio Matthew DeTullio
              Reporter:
              dordor dor s
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated: