Our Jenkins installation has begun to experience some rather bad behavior. Several plugins - namely the Promotion one - and downstream build tracking has begun to fail. After investigating it, I found that the problem is the fingerprinting. For every failure, the job that created some file and fingerprinted it would report "outside Jenkins" for the file's fingerprint origin instead of "this build". Looking up in the fingerprint in Jenkins shows it be reference in all the expected places, but Jenkins didn't think it originated within Jenkins.
I know for certain that the job is creating the file; it's a modified text file with a number of job-and-build specific text strings embedded in it, including the Jenkins build ID, which is ALWAYS unique. Logs show the file being created and fingerprinted. It's just that Jenkins doesn't consider the fingerprint to have originated with this build. Has anyone seen something similar? Is their a resolution to this? I'm using the latest Jenkins - v1.464 Thanks in advance, Jason Swager
