Commit Changes from Global Pipeline Libraries Polluting History

[Elmar Weber]

Hello,

we are using for some global shared pipeline libraries from git
repositories. When we now have a multibranch pipeline build and it
detects a new commit on the actual job repository, it does not just list
the changes of the pipeline job, but also from the global library in the
list of changes (see screenshot*). I guess because it checks it out as
part of the build flow.

My question:
- is this intended behaviour, or a bug?
- if intended, can I prevent this somehow?


* In the screenshot on the first entry is actually from the commit
triggering the pipeline. The others are changes from the global pipeline
libraries (which contains the scripts + configurations).

Thanks,
Elmar

[Baptiste Mathus]

For me it's a feature, the fact that you can see that the library changed (and could cause differences/failures) is valuable.

Now, maybe it could be categorized more clearly in the stage view plugin. But on the main build page it is already clearly separated for instance.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/9db040f4-114e-a4bd-bc4e-b6d3b46c8c48%40elmarweber.org.
For more options, visit https://groups.google.com/d/optout.

[Mark Waite]

I agree with Baptiste that I consider it a valuable feature to know when changes happen in a global pipeline library on which I depend.

Mark Waite

[Kevin Burnett]

i agree with Baptiste and Mark that it is potentially valuable to know when changes happen in a library on which you depend.

but in our case, we rarely do care. we're depending upon things like build and deployment script repos, an enormous pile of acceptance test repos, etc.

what i think i really want is the ability to indicate in my pipeline which repos i care enough about to have their changes bubbled up into the UI.

i attached another screenshot where the UI related to this hurts us. the left nav of an individual build includes two unlabeled links for each repo i don't care about. :)

i love jenkins and declarative pipelines btw, thanks for all you guys do!

[Elmar Weber]

Hello everyone,

thanks for the feedback, it make sense. I agree that an indication /
grouping by repo would solve the issue as well. Main reason it is
confusing is because it's not clear what triggered the build here, you
have to dig a bit to figure it out. I'll summarize this and post it as a
feature suggestion in the Jenkins tracker to have the discussion there
if it makes sense to get implemented.

Best,
Elmar

> --
> You received this message because you are subscribed to the Google
> Groups "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send

> an email to jenkinsci-use...@googlegroups.com
> <mailto:jenkinsci-use...@googlegroups.com>.

> To view this discussion on the web visit

> https://groups.google.com/d/msgid/jenkinsci-users/d7f268c2-e3f8-469c-bac6-0be1c6ca51a1%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/d7f268c2-e3f8-469c-bac6-0be1c6ca51a1%40googlegroups.com?utm_medium=email&utm_source=footer>.