|
||||||||
|
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.
If during comparing the current workspace (stored locally on the Jenkins site in a SQL database) with the current content of the SCM archive it becomes obvious, that the database scheme of that local database needs DB schema versioning, the SCM plugin should either try to automatically perform DB schema versioning for that job or if that can't be done, it would be a good idea to fall back to "Clean workspace" operation mode and start over with the local database (instead of compiling old workspace content and rating it "OK").