Hi, Does anyone have experience with setting up [url=http://continuousdelivery.com/2010/08/continuous-delivery-vs-continuous-deployment/]Continuous Delivery / Continuous Deployment[/url] for a Magnolia implementation?
If so, how did you set it up? We want to implement Continuous Delivery to our test environment using our Continuous Integration infrastructure using Git, Maven, Hudson and Nexus. Right now we think we want to create this test environment from scratch for every deployment which comes down to: * delete the Magnolia database tables in MySQL * remove the Magnolia Jackrabbit repository folders * deploy the new Magnolia WAR to Tomcat * install Magnolia * perform additional steps specific for this environment (i.e. set up defaultURI, subscribers etc) cheers, All of this automatically of course. Alternatively we could work with Magnolia module updates and leave the database intact. But that has the drawback that we do not test a clean install and that we always need to deploy a new version of our modules (or else the Magnolia version handlers will not be triggered). Any ideas? Edgar -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=18e003d6-1ed0-49cf-8f3b-4ebc4502e5ae ---------------------------------------------------------------- For list details, see http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
