|
||||||||
|
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.
Your suggestion sounds like a lot of work - our Jenkins contains nearly 200 jobs with integrity-plugin usage and hundreds of builds in history of many jobs...
In spite of that I have tried to getting the plugin version 1.17 to work (on a testsystem) - without success.
*Reconfiguring existing jobs (remove all history builds, remove integrity-plugin usage and re-add usage)
*New jobs (with and without copying configuration from other jobs)
*Deinstallation of PTC Integrity Plugin 1.12 after deletion of all jobs and installation of PTC Integrity Plugin 1.17
*Complete deletion of jenkins configuration directory and installation of PTC Integrity Plugin 1.17 in a new empty Jenkins
All attempts fails with the same SQLException.
Do you have any further ideas?
Many thanks in advance for your support.