chriseldredge / vulcan

Continuous Integration server
GNU General Public License v2.0
0 stars 1 forks source link

Rewrite build outcome store with RDBMS #110

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
The method of storing and loading build outcomes (using a spring xml file)
is way too slow for producing reports quickly.

Replace the existing persistence with an hsqldb instance.  Use standard sql
and jdbc so end users can connect their own datasources via JNDI.

Original issue reported on code.google.com by chris.eldredge@gmail.com on 15 Sep 2007 at 6:11

GoogleCodeExporter commented 9 years ago
Committed initial implementation in r434.  Still need to write conversion 
utility to
provide upgrade path for existing users.  Also need to refactor higher level 
code to
take advantage of faster implementation.

Original comment by chris.eldredge@gmail.com on 18 Sep 2007 at 1:14

GoogleCodeExporter commented 9 years ago

Original comment by chris.eldredge@gmail.com on 19 Sep 2007 at 4:21

GoogleCodeExporter commented 9 years ago
Two outstanding issues:

Maven builds that fail are not getting the target/message persisted properly, 
see
http://vulcan-project.org/live/viewProjectStatus.do?transform=xhtml&projectName=
vulcan&buildNumber=260

HSQLDB crashes on shutdown of tomcat, maybe calling "shutdown" is unnecessary.

Original comment by chris.eldredge@gmail.com on 21 Nov 2007 at 1:10

GoogleCodeExporter commented 9 years ago
Need to fix:

Dashboard does not show newest builds after conversion completes.
Remove "shutdown" code, verify that Tomcat shutdown works

Original comment by chris.eldredge@gmail.com on 3 Dec 2007 at 3:18

GoogleCodeExporter commented 9 years ago
Also need to check commons-dbcp configuration.  autocommit should be disabled 
and
stay that way.

Original comment by chris.eldredge@gmail.com on 3 Dec 2007 at 3:39

GoogleCodeExporter commented 9 years ago
r5: set default autocommit to false in dbcp config, however passivateObject 
still
sets autocommit to true.  See DBCP-102 and DBCP-97:

https://issues.apache.org/jira/browse/DBCP-102?page=com.atlassian.jira.plugin.sy
stem.issuetabpanels:all-tabpanel
https://issues.apache.org/jira/browse/DBCP-102?page=com.atlassian.jira.plugin.sy
stem.issuetabpanels:all-tabpanel

Original comment by chris.eldredge@gmail.com on 4 Dec 2007 at 6:00

GoogleCodeExporter commented 9 years ago
This has been in beta and working properly using both mysql and hsqldb.  
Additional 
problems will  be addressed in separate issue reports.

Original comment by chris.eldredge@gmail.com on 4 Nov 2008 at 4:14