|
||||||||
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
I noticed this too but I actually use this feature. I have carefully configured my jobs so that...
I then use the presence of a "/" in the fingerprint filename in the build.xml file to distinguish between artifacts generated by a build and artifacts consumed by it. I know it is a horrible hack but it allows me to detect statically when a build needs to be rerun due to an updated upstream artifact.
I'd love to hear a better suggestion for how to do this.