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