|
||||||||
|
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/d/optout.

Code changed in jenkins
User: Cletus D'Souza
Path:
pom.xml
src/main/java/hudson/scm/DerbyUtils.java
src/main/java/hudson/scm/IntegrityCMProject.java
src/main/java/hudson/scm/IntegrityRevisionState.java
src/main/java/hudson/scm/IntegritySCM.java
src/main/resources/hudson/scm/IntegritySCM/config.jelly
src/main/resources/hudson/scm/IntegritySCM/global.jelly
http://jenkins-ci.org/commit/integrity-plugin/43ad415f293ffc23861b23fa4caae3d7ef52da7c
Log:
Moved from single derby db for each job/build to a single db for the
entire Jenkins instance. Relevant issues are:
JENKINS-25228 - Using the integrity-plugin together with concurrent
builds causes SQL Exceptions
JENKINS-14675- Schema 'DBUSER' does not exist error in integrity pluginJENKINS-25450- Unexpected behavior of Jenkins Integrity plugin afterSQL Exception inside plugin (no error returned to build job).