First published on MSDN on Oct 01, 2015
Upgrading Release Management is a fairly simple process, and the upgrade from 2013 to 2015 follows the same steps as updating Release Management 2013 to the latest 2013.4 Version.
We wanted to provide a short walkthrough with Screenshots for reference.
The account running the upgrade must be
- Local Admin on the Release Management Server Machine.
- SysAdmin on SQL Server (where the ReleaseManagement Database is hosted)
- Release Manager Role in the existing 2013 RM server for the upgrade.
We are going to upgrade Release Management 2013 update 4 to Release Management 2015 here,
It would be a good idea to make a note of the settings and account used in the current RM server to add the details during the new configuration.
1. Take Backup of the ReleaseManagement database.
First, we need to take a backup of the ReleaseManagement database. We’d need this backed up so we could go back to the previous working state, for disaster recovery/mitigate a failed upgrade.
2. Backup config files of RM Service and RM Web
It’s a good idea to take a backup of the config files, in case you have done any customizations. After upgrade, it is recommended that you
the changes to the new config files, and
not replace them
Backups of config files.
3. Uninstall Release Management Server 2013 Update 4.
Next, let’s uninstall RM 2013 update 4.
We need to uninstall older version to install the 2015 bits.
Click on Launch after setup or Release Management Server For Team Foundation Server 2015 from the Start Menu.
Enter the Database server where the RM 2013 database is present and click on “Apply Settings”
That’s it! The upgrade is done!
6. Install RM Client, Deployment agents
Similarly, uninstall previous versions of RM Client, agents and install the 2015 Versions.
Please note that the Previous Version of RM Clients will not connect to RM Server 2015. The 2013 Deployment agents would not auto-upgraded to 2015 (Major version upgrades will not happen)
So you'd have to manually install and reconfigure Deployment agent 2015 and uninstall the 2013 version.
7. Release management service and web, config file changes/update.
There could have been changes made to config files, such as ApprovalRequestEmailLanding, which enables to connect to online available release management web site via a mobile phone etc, to do release pipeline approvals. These changes need to be reapplied in release management web and service config files.
The backups of config files made in step 2 (
2. Backup config files of RM Service and RM Web.
) come in handy for this effort.
As mentioned earlier,
it is not advisable to replace the new configs entirely with backup config files.
Only required changes should be updated carefully to new config files referring the backup config files.
For example without the changes applied the email approval request link will not work without network or vpn connection to domain network which release management server belongs to.
View request here linked to local network url.
This can be updated in ApprovalRequestEmailLanding configuration in config files of web and service of the release management.
Once this is updated the online release management web site link in View Request for approval request emails is set by RM server.