Views

Prepare a new release environment

Share |

These actions should be done before or just after a major release to create a new major version environment.

  • Create a maintenance branch
  • Update Const.TEST_VERSION and Const.JAJUK_CODENAME constants
  • Change POM version

Updating development server to keep automatic build working

You need to create the new SVN maintenance branch prior doing these steps.

  • Update branch in hudson maintenance branch SCM configuration
  • On the hudson server : 
login as tomcat55
cd /data/hudson/jobs/Jajuk Daily Build - Maintenance/workspace
rm -rf *
mkdir jajuk tests
  • Change maintenance build.xml files

Edit branches/maintenance-1_5/src/scripts/build.xml

    • change version: 
      <property name='version' value='1.5.1_b1' />
    • change test value to "test": 
      <property name='test' value='test' />
    • change WAR name from jajuk-trunk-${test}.war to jajuk-${test}.war 
      <echo message=' JNLP war file in:      ${rootdir}/jajuk-${test}.war' />
    • change destination WAR name 
      <war destfile='${rootdir}/jajuk-${test}.war' webxml='${srcdir}/packaging/jnlp/web.xml'>
    • Commit changes
  • Change trunk build.xml files

Edit trunk/jajuk/src/scripts/build.xml

    • Change: version and test value to "test": 
      <property name='version' value='1.6dev_20080209' />
      <property name='test' value='test' />
    • Commit changes
Retrieved from "http://wiki.jajuk.info/index.php/Prepare_a_new_release_environment"