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.
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.
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