dsaydon90
(dordor)
September 22, 2024, 4:28pm
1
Hi,
I’m trying to hide git changelog/changeset about shared library within a Jenkins multibranch pipeline.
I’ve explored explored various options without success.
Let’s overview what I’ve tried and please let m know if there’s something I’m missing:
Options Explored:
option 1 : unchecked “Include @Library changes in job recent changes” from system global configurations
option 2 : add “changelog: false” to pipelines
Since I’m using various pipeline types I was able to tried them all:
example 1: library identifier: '<my shared lib>@<shared lib branch>', changelog: false
example 2: @Library(value='<my shared lib>@<shared lib branch>', changelog=false)
option 3 : clear ChangeSets and perform checkout
In this option we can run currentBuild.getChangeSets().clear() and then we chan perform git clone with checkout scm (or other git command).
However, this would require manual checkout, losing the benefit of automatic default checkout scm.
None of the 3 options above worked for me, and I’m still seeing the shared library changelog in my multibranch pipelines.
Any other solutions?
It seems there’s an open ticket (link ) related to hiding changesets, but I’m not quite sure if this ticket is also relevant for multibranch pipelines.
jenkins version: 2.462.2
hukel
October 16, 2025, 10:39am
3
Any other ideas for this? The problem applies to simple (single stage) pipelines, too. Every job’s console output is filled with these 20+ lines:
21:46:12 Started by user XYZ
21:46:12 Loading library xyz-shared@main:notifications/
21:46:12 Attempting to resolve main from remote references...
21:46:12 > git.exe --version # timeout=10
21:46:12 > git --version # 'git version 2.49.0.windows.1'
21:46:12 > git.exe ls-remote -h -- file:///c:/tools/jenkins_library # timeout=10
21:46:13 Found match: refs/heads/main revision 1aece44c1b542de9af60ea9d9427b10086a82beb
21:46:13 The recommended git tool is: NONE
21:46:13 No credentials specified
21:46:13 > git.exe rev-parse --resolve-git-dir C:\data\Jenkins\.jenkins\workspace\JOB NAME@libs\568c993389b5b6ef2f458b1b92e4a16e940df87d578c9ae18719b0b4f5e22761\.git # timeout=10
21:46:13 Fetching changes from the remote Git repository
21:46:13 > git.exe config remote.origin.url file:///c:/tools/jenkins_library # timeout=10
21:46:13 Fetching without tags
21:46:13 Fetching upstream changes from file:///c:/tools/jenkins_library
21:46:13 > git.exe --version # timeout=10
21:46:13 > git --version # 'git version 2.49.0.windows.1'
21:46:13 > git.exe fetch --no-tags --force --progress -- file:///c:/tools/jenkins_library +refs/heads/*:refs/remotes/origin/* # timeout=10
21:46:13 Checking out Revision 1aece44c1b542de9af60ea9d9427b10086a82beb (main)
21:46:13 > git.exe config core.sparsecheckout # timeout=10
21:46:13 > git.exe checkout -f 1aece44c1b542de9af60ea9d9427b10086a82beb # timeout=10
21:46:14 Commit message: "added instructions to readme"
21:46:14 > git.exe rev-list --no-walk 1aece44c1b542de9af60ea9d9427b10086a82beb # timeout=10
21:46:14 [Pipeline] Start of Pipeline
Our users would prefer not to see all of message unrelated to pipeline steps.
MarkEWaite
(Mark Waite)
October 16, 2025, 8:15pm
4
You’re asking a different question than the original question in this topic. The original topic is related to not included the changelog from the shared library in the changelog of the job that is using the shared library. You are asking to hide a section of the console log. They are very different questions.
An enhancement request asks to optionally reduce the verbosity of the logging done by the git client plugin.
panicking
(Michael Nazzareno Trimarchi)
October 17, 2025, 6:55pm
5
I think that include the changes of the library in pipeline has no sense if the checkbox is disabled. For the console output I really don’t think that it’s a problem
hukel
December 15, 2025, 12:08pm
6
Thank you for clarifying about the difference. The latest version of the issue you mentioned is here:
opened 02:58PM - 18 Aug 14 UTC
imported-jira-issue
component:git-client-plugin
resolution:unresolved
priority:minor
<p>The git plugin currently prints out the git commands that it executes.</p>
… <pre>
git rev-parse master^{commit} # timeout=10
</pre>
<p>In some cases, these commands can be numerous and thus distract the user from other pertinent information in the build log.</p>
<p>It would be very valuable to be able to enable or disable this verbose output via a option in the job configuration.</p>
---
<details><summary><i>Originally reported by <img align="left" width="20" src="https://raw.githubusercontent.com/jenkinsci/artifacts-from-jira-issues/refs/heads/main/avatars/scoheb.png" title="scoheb's avatar" /> <a href="https://issues.jenkins.io/secure/ViewProfile.jspa?name=scoheb">scoheb</a>, imported from: <a class="original-jira-link" href="https://issues.jenkins.io/browse/JENKINS-24304" target="_blank">Enable/Disable verbose Git command logging in Jenkins build log</a></i></summary>
<i><ul>
<li><b>status</b>: Open
<li><b>priority</b>: Minor
<li><b>component(s)</b>: git-client-plugin
<li><b>resolution</b>: Unresolved
<li><b>votes</b>: 13
<li><b>watchers</b>: 14
<li><b>imported</b>: 20251211-071809
</ul></i>
<details><summary>Raw content of original issue</summary>
<pre>
<p>The git plugin currently prints out the git commands that it executes.</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
<pre class="code-java">git rev-parse master^{commit} # timeout=10
</pre>
</div></div>
<p>In some cases, these commands can be numerous and thus distract the user from other pertinent information in the build log.</p>
<p>It would be very valuable to be able to enable or disable this verbose output via a option in the job configuration.</p>
</pre>
</details>
</details>