|
||||||||||||||
|
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/groups/opt_out.
We just hit this problem with one of the jobs. The scenario was that the faulty commit was pushed to the repo, it was built in Jenkins, then it was reset --hard to previous commit and force pushed. After that the workspace was wiped out and now I can't build the job because it complains that it can't find the last built revision which it tries to start with.
Jenkins 1.509, git plugin 1.1.23