|
||||||||
|
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/groups/opt_out.
The same problem here. Once a commit is made during the time when SVN server is out of sync (let's say one month ahead the current time), there is no way for you to have the job check out the latest rev again(it's always stuck at some rev ahead of that "guilty" commit). Although I've tried to clean up the working copy & check out again. The only workaround is added @HEAD to the repo URL. This is really frustrating![]()