Details
-
Improvement
-
Status: Open (View Workflow)
-
Trivial
-
Resolution: Unresolved
Description
By using a global shared library for Pipeline jobs, rawBuild.changeSets on the current build will contain the changes of the global shared library and the repository that is used for building. To better distinguish between theses to sources, it would be great to have a variable to obtain the repository.
The GitChangeSet class does not provide any possibility to get repository information about the commit.
currentBuild.rawBuild.changeSets.collect { cs ->
cs.collect { entry ->
"* ${entry.author.fullName}: ${entry.msg}"
}.join("\n")
}.join("\n")
Attachments
Issue Links
- is related to
-
-
- Open
-
- relates to
-
JENKINS-39499 There is no way to set changeSet property of shared library checkout to false
-
- Resolved
-
Activity
currentBuild.rawBuild.changeSets is deprecated; use currentBuild.changeSets.
Probably there should be something in the form of a map, keyed by SCM.getKey().
This feature would be really appreciated as we would like to trigger certain actions when a specific file is changed, but since we are also using a shared-pipeline, things become a bit wonky to figure out if the change in question is in the shared-pipeline or in the repository in question, because the file-name exists in both repos.
Hans-Eric Jönsson
added a comment - - edited This feature would be really appreciated as we would like to trigger certain actions when a specific file is changed, but since we are also using a shared-pipeline, things become a bit wonky to figure out if the change in question is in the shared-pipeline or in the repository in question, because the file-name exists in both repos.
This would be a boon for us too. I don't mind having the changes, but I'd like to be able to filter them.