Details
-
Improvement
-
Status: Resolved (View Workflow)
-
Major
-
Resolution: Duplicate
-
None
Description
There is no configuration anywhere that would make use of fingerprints (e.g. in downstream jobs). Still Jenkins "always" writes fingerprints of jar files.
As far as I understood https://wiki.jenkins-ci.org/display/JENKINS/Fingerprint this should ony happen if configured explicitly.
Because of the huge amount of fingerprints (138206 for now) we're running into performance issues.
We're currently running 1.509.1 LTS
Attachments
Issue Links
- duplicates
-
-
- Resolved
-
Activity
Most of our jobs are Maven jobs. What's the link between Maven jobs and fingerprints?
kutzi
added a comment - Maven jobs do automatically fingerprint all artifacts which are consumed (i.e. dependencies) and produced by a job
kutzi
added a comment - Maven jobs do automatically fingerprint all artifacts which are consumed (i.e. dependencies) and produced by a job kutzi
added a comment - BTW: this doesn't seem to be related to the fingerprint plugin. Changing component to core
kutzi
added a comment - BTW: this doesn't seem to be related to the fingerprint plugin. Changing component to core 
Martin Nattrodt
added a comment - The fingerprints are calculated even if archiving is disabled. In this case fingerprints are just nonsense.
I would expect, that fingerprints are only calculated for archived files.
Martin Nattrodt
added a comment - The fingerprints are calculated even if archiving is disabled. In this case fingerprints are just nonsense.
I would expect, that fingerprints are only calculated for archived files.
Are you using the Maven job type?