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

There is no way to set changeSet property of shared library checkout to false

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      Once we have Shared Library sources in the same repository under different branch, all changes are made to the shared library scripting are listed in the list of build changes. The reason is perhaps that the pipeline shared library checkout is done using the pipeline generic checkout step with the changeset property set to true.

      Could you provide way how to control it using the global settings or disable it by default as you are rather interested in sources changes than in the pipeline scripting changes please?

        Attachments

          Issue Links

          duplicates

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-41497 Poll SCM and Timer triggers include "Changes" for a Pipeline for any/all Shared Libraries

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

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-40129 Extend GitChangeSet to get the repository name

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

            Activity

            Descending order - Click to sort in ascending order
            Hide
            Permalink
            kenneth_s_brooks Kenneth Brooks added a comment - - edited

            Same issue for us.

            We have lots of multibranch builds all using a global shared library that we are building.

            Every change for the library shows up in the changeset of the target app build.
            Also, the status of the target app build shows up against the commits of the global libraries in bitbucket.

            I agree with the OP suggestion of defaulting the changeset to false. Perhaps with the ability to override globally in the configs.

            I haven't pulled the code but I believe it is this line:
            https://github.com/jenkinsci/workflow-cps-global-lib-plugin/blob/master/src/main/java/org/jenkinsci/plugins/workflow/libs/SCMSourceRetriever.java#L90

            delegate.setChangelog(true); // TODO is this desirable?
            Show
            kenneth_s_brooks Kenneth Brooks added a comment - - edited Same issue for us. We have lots of multibranch builds all using a global shared library that we are building. Every change for the library shows up in the changeset of the target app build. Also, the status of the target app build shows up against the commits of the global libraries in bitbucket. I agree with the OP suggestion of defaulting the changeset to false. Perhaps with the ability to override globally in the configs. I haven't pulled the code but I believe it is this line: https://github.com/jenkinsci/workflow-cps-global-lib-plugin/blob/master/src/main/java/org/jenkinsci/plugins/workflow/libs/SCMSourceRetriever.java#L90 delegate.setChangelog( true ); // TODO is this desirable?
            Hide
            Permalink
            tobilarscheid Tobias Larscheid added a comment -

            We also stumble across this annoying issue, a fix would be highly appreciated.

            Show
            tobilarscheid Tobias Larscheid added a comment - We also stumble across this annoying issue, a fix would be highly appreciated.

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              martin_fousek Martin Fousek
              Votes:
              4 Vote for this issue
              Watchers:
              6 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: