|
||||||||
|
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 common theme here seems to be when migrating from an older version of the plugin to a newer version. Especially when there's been architectural changes with the way the plugin stores retrieves its cache information. While I make an attempt to prevent such changes, it can't be avoided completely. This is especially true in the past.
Going forward, I don't anticipate any major changes to the plugin's architecture as it relates the the derby database. Can I get a consensus that re-creating the job and/or repeated builds (which is essentially re-creating the derby db) resolves this issue?
Thanks!
Cletus