|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
A specific version can be checked out by specifying the SHA1 hash as the "branch to build". I created a parameterized build with a parameter "SHA1" and the string "${SHA1}" as the branch to build. I was using the git-client-plugin repository for the test, so I passed the parameter value "git-client-1.6.1". It performed the checkout and the build of that tag.
I did the same with a SHA1 hash, and it checked out that SHA1 as well.
Is there a way your upstream job could provide the SHA1 to the downstream job as a parameter?
I'd prefer to close this as "not a bug", but would like your confirmation that the technique works for you.