So, do you mean that we should accurately select only the artifacts
that we create ourselves? That indeed makes sense. I still wonder
how the maven plugin works though since it does that automatically,
it can definitely fingerprint the build products by checking the pom
file, but I wonder about how
I'm not using pipeline jobs, but the "normal" configuration. There I can
tell Jenkins, what to fingerprint (paths and wildcards)
You need to be (very) careful what you fingerprint. If I understood that
correctly, the algorithm used is
- fingerprint whatever the user asks CI t fingerprint (MD5 c
Hi, I'm trying to create a new set of pipeline builds for a number of
modules.
The modules are built with gradle and have dependencies between themselves.
I'd like to leverage the fingerprinting feature in Jenkins to obtain
upstream and
downstream relationship created automatically, but I'm not c
