Hi All,
After the reorg is complete I was thinking that moving to something
like CruiseControl for our automated builds would be good.
I propose;
1) Using CruiseControl for the automated builds
a) continuous builds - every check-in would do a build and
report to the dev list any error discovered
b) historic reports from the JUnit and cactus tests
c) automate the tagunit tests so we get consistent deployment on
WLS 8.1.x
2) Using Cargo (http://cargo.codehaus.org) to start and stop the
various app server instances (tomcat, orion etc)
a) We could use this to make sure that all the 'supported' app
servers actually work with the examples
3) Use Cannoo webtest to preform sanity tests on all app server
instances
a) along with 2 would provide a means to make sure that at least
our examples will work with all the 'supported' web containers
I would be glad to host this continuous build process on dudney.net.
Thoughts?
TTFN,
-bd-
