History log

May 2010

1. Configured application to store their data in dedicated repository folders.  This will facilitate more effective backup and restore.
2. Disabled Ubuntu keyring.  This enables the CM Appliance applications to manage the storage of user application usernames and passwords without any interference from Ubuntu.
3. Updated the maven settings.xml file to store the SCM and Artifactory usernames and passwords.
4. Enhanced Artifactory security; created dedicated reader and publisher user groups and configured library access rights to prevent updates and deletion by anonymous or readers.
5. Installed and configured Twiki.  Twiki is a Perl based collaboration and document management application.
6. Upgraded Hudson to use the official Ubuntu installation package rather than the standalone Hudson war file.
7. Changed the deployment process.  Instead of packaging the complete virtual machine into a single zip file the virtual machine is now made up of a self installing split WinRar archive.

April 2010

1. Appliance made available as a download from this website.

March 2010

1. Upgraded all applications to latest versions.
2. Upgraded Jira to use Mysql database.
3. Enabled integration between Jira and Subversion.
4. Created Hudson continuous integration job.  Hudson integrates with Subversion and kicks off a Maven build when code is checked into Subversion.
5. Modified installed applications so that they run as Configman rather than root.
6. Enhanced Jira service script to include auto shutdown when the server is shutdown.
7. Installed Bamboo and created Bamboo continuous integration job.

December 2009

1. Added virtual disk to store the appliance applications and data.
2. Implemented start-up and shutdown scripts as Linux service start-up and shutdown scripts.

November 2009

1. First implementation of CM Appliance.