Any thoughts, anyone? Thanks. On Sat, Dec 14, 2013 at 10:47 AM, Maureen Barger <mobar...@gmail.com> wrote: > Hi - Our process is probably like many of yours - > Build something - run regression - promote build on test success > > In between those steps we copy artifacts from the build to fingerprint the > jobs. > > We use this process for several code streams simultaneously, each > running their own builds from their own SVN paths and running their > own suite of tests. > > Overnight one code stream started promoting another's builds. The > error was from the build that was promoted erroneously was: > WARNING: SOME_OTHER_BUILD appears to use this job as a promotion > criteria, but no fingerprint is recorded. Fingerprint needs to be > enabled on both this job and SOME_OTHER_BUILD. See > http://hudson.gotdns.com/wiki/display/HUDSON/Fingerprint for more > details > > When I look at fingerprint history of SOME_OTHER_BUILD, it has recent > fingerprints that pertain to its own code and tests. Yet looking back > a week, it does have fingerprints from the build that was erroneously > promoted. > > So my questions are - > 1) are fingerprints cumulative? Meaning the process by which they are > inspected looks at ALL of them and not just those associated with the > particular build? > 2) If so is there a way to clean these up? > 3) I suspect the older fingerprints were copied to newer build job > because the job was created as a copy of the old job. I am realizing > that all aritifacts get copied to new job as a result. Is this a true > assessment? > > Thanks.
-- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
