In this procedure, we assume that installation directory of 4.0.61 or 4.0.61 server is _/quickbuild-old_, and new version of QuickBuild is extracted to directory _/quickbuild-new_.
# Login to old QuickBuild web UI as administrator, switch to menu _Administration/Database Backup_, and backup the database to file _backup.zip_. After the backup, you should be able to find the file _/quickbuild-old/backup.zip_.
# Stop old QuickBuild server process. On Windows platform, please also run _/quickbuild-old/bin/server.bat remove_ to unregister the QuickBuild NT service if it is installed previously. On Windows Vista and Windows 7 system with UAC enabled, you will need to run this command as administrator.
# Copy all files under _/quickbuild-old/conf_ to _/quickbuild-new/conf_ *except for* _wrapper.conf_ and _wrapper_license.conf_.
# Edit file _/quickbuild_new/conf/hibernate.properties_ to remove below line:
{code}hibernate.hbm2ddl.auto=update{code}
# If you've adjusted memory setting (property _wrapper.java.maxmemory_), and java command (property _wrapper.java.command_) in _/quickbuild-old/conf/wrapper.conf_, make the same adjustment in _/quickbuild-new/conf/wrapper.conf_.
# If you run QuickBuild with Sun JDK or [OpenJDK|http://openjdk.java.net], make sure to edit file _<QuickBuild install dir>/conf/wrapper.conf_ and add below entry to avoid using up permgen space:
{code}wrapper.java.additional.4=-XX:MaxPermSize=256m{code}
# Copy all files under the _/quickbuild-old/asset_ to _/quickbuild-new/resource_ *except for* _default_html_notification.vm_, _default_plain_notification.vm_, and _velocity.properties_.
# If you are connecting to external database in old QuickBuild (please check file _/quickbuild-old/conf/hibernate.properties_ for sure), manually delete the database using your database tool, and create a new one with the same name.
# Open a command line window, switch to directory _/quickbuild-new/bin_, and run command _restore.(bat|sh)_ /quickbuild-old/backup.zip_ to migrate and restore data of old QuickBuild.
# Run command _/quickbuild-new/bin/server.bat install_ to install QuickBuild NT service if necessary. On Windows Vista and Windows 7 system with UAC enabled, you will need to [open the command prompt window as Administrator|http://www.howtogeek.com/howto/windows-vista/run-a-command-as-administrator-from-the-windows-vista-run-box/] before running command _/quickbuild-new/bin/server.bat install_.
# Startup new QuickBuild server by running _/quickbuild-new/bin/server.bat console_ and check if data has been restored successfully.
# Build and user agents may not get started automatically after upgrade. You may check inactive node list from grid page and start them manually by logging to the machine with appropriate users and running command _<agent install dir>/agent.(sh|bat) start_. This only happens when upgrading QB4 to QB5 as 5.0 introduces the bootstrap upgrading mechanism but unfortunately cause the agent to stop for the first upgrade. After this start, the agent will be able to update and start automatically when upgrade to new versions even if the bootstrap libraries are changed.
# Verify server and agent installation by running some builds.
# Login to old QuickBuild web UI as administrator, switch to menu _Administration/Database Backup_, and backup the database to file _backup.zip_. After the backup, you should be able to find the file _/quickbuild-old/backup.zip_.
# Stop old QuickBuild server process. On Windows platform, please also run _/quickbuild-old/bin/server.bat remove_ to unregister the QuickBuild NT service if it is installed previously. On Windows Vista and Windows 7 system with UAC enabled, you will need to run this command as administrator.
# Copy all files under _/quickbuild-old/conf_ to _/quickbuild-new/conf_ *except for* _wrapper.conf_ and _wrapper_license.conf_.
# Edit file _/quickbuild_new/conf/hibernate.properties_ to remove below line:
{code}hibernate.hbm2ddl.auto=update{code}
# If you've adjusted memory setting (property _wrapper.java.maxmemory_), and java command (property _wrapper.java.command_) in _/quickbuild-old/conf/wrapper.conf_, make the same adjustment in _/quickbuild-new/conf/wrapper.conf_.
# If you run QuickBuild with Sun JDK or [OpenJDK|http://openjdk.java.net], make sure to edit file _<QuickBuild install dir>/conf/wrapper.conf_ and add below entry to avoid using up permgen space:
{code}wrapper.java.additional.4=-XX:MaxPermSize=256m{code}
# Copy all files under the _/quickbuild-old/asset_ to _/quickbuild-new/resource_ *except for* _default_html_notification.vm_, _default_plain_notification.vm_, and _velocity.properties_.
# If you are connecting to external database in old QuickBuild (please check file _/quickbuild-old/conf/hibernate.properties_ for sure), manually delete the database using your database tool, and create a new one with the same name.
# Open a command line window, switch to directory _/quickbuild-new/bin_, and run command _restore.(bat|sh)_ /quickbuild-old/backup.zip_ to migrate and restore data of old QuickBuild.
# Run command _/quickbuild-new/bin/server.bat install_ to install QuickBuild NT service if necessary. On Windows Vista and Windows 7 system with UAC enabled, you will need to [open the command prompt window as Administrator|http://www.howtogeek.com/howto/windows-vista/run-a-command-as-administrator-from-the-windows-vista-run-box/] before running command _/quickbuild-new/bin/server.bat install_.
# Startup new QuickBuild server by running _/quickbuild-new/bin/server.bat console_ and check if data has been restored successfully.
# Build and user agents may not get started automatically after upgrade. You may check inactive node list from grid page and start them manually by logging to the machine with appropriate users and running command _<agent install dir>/agent.(sh|bat) start_. This only happens when upgrading QB4 to QB5 as 5.0 introduces the bootstrap upgrading mechanism but unfortunately cause the agent to stop for the first upgrade. After this start, the agent will be able to update and start automatically when upgrade to new versions even if the bootstrap libraries are changed.
# Verify server and agent installation by running some builds.