|
||||||||
|
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've tried it, but it seems that fact, that I have several upstream jobs that trigger a same downstream deployment job and that all are using same "revision.txt" makes it hard for Jenkins to manage.
Maybe I should create "projecta_revsision.txt", "projectb_revision.txt" in upstream job and pass that filename as a build parameter to downstream job. Then in fingerprint screen I won't see messages like "revision.txt" was introduced by "projecta" and last used by "projectb".