+4420 3290 2266

info@coldcore.com

Project Haala

Documentation

Release process Release process, versions and change log

This describes the release proccess which the project follows. It consists of the current version being released, pushed to the GIT server, deployed to LIVE environment and the next version being started. The process follows this article http://nvie.com/posts/a-successful-git-branching-model

Commit the version

  1. Switch to develop branch and merge all features into it
  2. Run scripts to remove SNAPSHOT from version in generic and every releasing pack
    versions-generic.sh
    versions-cactus.sh
  3. Go through every pom.xml and fix parent versions by removing SNAPSHOT
  4. Clean rebuild generic and packs
    Note: LIVE build requires tomcat-live maven profile enabled
  5. Check release.info file in WAR to ensure the proper release was assembled
  6. Commit develop changes to GIT (message Release X.XX)
  7. Switch to master branch and merge develop into it and then tag it (message Release X.XX)
    git tag -a X.XX
  8. Push to the GIT server
    git push
    git push --tags

Deploy to LIVE

  1. Copy resources to server
  2. Optionally suspend the system and warn online users via admin
  3. Switch Apache to display down pages
  4. Stop Tomcat
  5. Apply patches to DB
  6. Copy feed files into feed directory
  7. Deploy the package and clean Tomcat temporary/work files (optionally)
  8. Start Tomcat
  9. Wait for Tomcat to start and eat feeds
  10. Switch Apache to normal mode

Increment the version

  1. Switch to develop branch
  2. Run scripts to increase and add SNAPSHOT to version in generic and every pack
  3. Go through every pom.xml and fix parent versions by adding SNAPSHOT
  4. Commit develop changes to GIT (message Version up)
  5. Push to GIT server
  6. Rebase features from develop
sitemap