Testing upgrades and EAP best practices

I currently use 4.5.4 and I'd like to upgrade to 5.0.3.  I'd also like to be able to start playing with the 5.1 EAP.  My organization would like to put together staging deployments of TeamCity to test and refine our upgrade process.  What are the best practices for doing so?

5 comments

David,

You should probably create separate installations for newer TeamCity versions (preferable on dedicated computer) and ensure they use own copies of data (.BuildServer and database). If you need to just test-drive upgrade process, you probably won't need build artifacts and build logs of the production installation.

I've compiled quick instructions on the process that you might find useful.

Please make sure each instalaltion uses own copies of the data files and database and make backups.

If you will have any feedback on the upgrade process, please let us know.

0

We use Enterprise Edition.  Will we need to purchase another license in order to set up another installation for test-driving purposes?

0

David,

You can use evaluation license for the test server.
Also, if you are using it only for the testing purposes I guess you can temporarily use your existing license.

0

Before we can test the upgrade process and latest version in our staging system, we need to get a copy of the current TeamCity running.  As mentioned before, our current version is 4.5.4.  How can we get an evaluation license for version 4.5.4?
Using our existing license doesn't seem feasible.  When we copied over the <TeamCity Data Directory> from our current TeamCity to the staging TeamCity, the Administration page was inaccessible until we deleted the license file from <TeamCity Data Directory>.

We're also experiencing problems with our project configurations.  We've been following the steps enumerated here: http://confluence.jetbrains.net/display/TCD5/How+To...#HowTo...-MoveTeamCityinstallationtoanewmachine , and after following all the steps and logging in there's a critical error message for each project that contains one or more build configuration:

Critical error in configuration file E:\TeamCity\config\<ProjectName>\project-config.xml:
org.jdom.input.JDOMParseException: Error on line 8 of document file:/<TeamCity Data Directory>/config/<ProjectName>/project-config.xml: Element type "settings" must be declared.


We verified the <settings /> tag is declared as a child of each <build-type /> tag in our project config files.  All rows in the projects table in our external DB got deleted as well.  This problem is particularly confounding and any advice on how to resolve it would be greatly appreciated.  Thanks!
0

David,

> How can we get an evaluation license for version 4.5.4?

You can contact our sales department at sales@jetbrains.com


> Using our existing license doesn't seem feasible.  When we copied over the <TeamCity Data Directory> from our current TeamCity to the staging TeamCity,
> the Administration page was inaccessible until we deleted the license file from <TeamCity Data Directory>.

I am not sure this is related. If you use the same TeamCity version (binaries) and the same content of the data directory, there should be no difference between your production and test server.
If you do use the same binaries and data, please provide the server logs and describe how the page was inaccessible.


> there's a critical error message for each project that contains one or more build configuration

Most probably the configs were not converted to the newer format. The most common reason for this can be not copied ".BuildServer/system/version.dat" file. You should probably repeat all over again.

Please try to copy the dataabse and data directory and run the same TeamCity version as you have installed. When it runs OK, proceed with the upgrade.

0

Please sign in to leave a comment.