Details
-
Bug
-
Status: Resolved (View Workflow)
-
Major
-
Resolution: Duplicate
-
None
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
-
JENKINS-41497 Poll SCM and Timer triggers include "Changes" for a Pipeline for any/all Shared Libraries
-
- Reopened
-
- relates to
-
JENKINS-40129 Extend GitChangeSet to get the repository name
-
- Open
-
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