|
||||||||
|
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 think I found a good workaround for the problem:
When you have a faulty commit pushed and Jenkins already built, it instead of going into the project workspace and trying to reset --hard it there do the "git reset --hard" operation from the execute shell build step. IT will find the previous build revision no problem and then this command will put the project into the state you need and record that last build revision properly. There will be no issues!
I hope that helps!