![]() ![]() Make sure to preserve the TeamCity Data Directory and the database intact (making a backup beforehand), backing up and restoring previously customized settings (for example, in. #Teamcity upgrade upgrade#The general approach to upgrade is to remove all the files of the previous installation in the TeamCity Server Home and place the new files into the same location. If you have customized TeamCity installation (like Tomcat server settings change), you will need to repeat the customization after the upgrade. On upgrade, all the TeamCity configuration settings and other data are preserved unless noted in Upgrade Notes. However, when upgrading to the next major version (changed YYYY.N), you will not be able to downgrade with the data preservation: you will need to restore a backup of the appropriate version. The general policy is that bugfix updates (indicated by changes in the B part of the YYYY.MM.B TeamCity version) do not change data format, so you can freely upgrade/downgrade within the bugfix versions. Unless specifically noted, downgrades with preserving the data are not possible with changing the major version and are possible within bugfix releases. TeamCity supports upgrades from any of the previous versions to the current one. Review the Licensing Policy page and the Licensing and Upgrade section on the official site. When upgrading from TeamCity 4.x or earlier, note that the licensing policy in TeamCity versions 5.0 and later are different from that of the previous TeamCity versions. To extend the evaluation period, contact the JetBrains sales department. Note that each TeamCity version can be evaluated only once. #Teamcity upgrade license#If you are only evaluating a newer version, you can get an evaluation license on the download page. If not all the licenses cover the target version release date, consider renewing the licenses before the upgrade (you can replace the old license keys with the renewed ones even before the upgrade). Typically all the minor updates (indicated by changes in the B part of the YYYY.MM.B TeamCity version) use the same effective release date (that of the major release). Check the effective release date on the release list. The licenses are valid only for the versions of TeamCity with the effective release date within the maintenance period. You will need the backup to roll back to the previous version in the unlikely event of the upgrade failure.īefore upgrading, make sure the maintenance period of your licenses is not yet elapsed (use the Administration | Licenses page to see your license keys). If you have non-bundled plugins installed, check plugin pages for compatibility with the new version and upgrade/uninstall the plugins if necessary.īack up the current TeamCity data including settings, database, and supplementary data. Before Upgradeįor a major upgrade, review what you will be getting in What's New.Ĭheck your license keys unless you are upgrading within bugfix releases of the same major YYYY.MM version.ĭownload the new TeamCity version (see links to all released versions).Ĭonsider probing the upgrade on a test server. This way, you run a fully supported version with the latest fixes and security patches. It is recommended to plan for regular upgrades to run the latest TeamCity version at least after several bugfix updates are released. All the settings and data are preserved unless noted in the Upgrade Notes. TeamCity supports upgrades from any of the previous versions to the later ones. It is strongly recommended backing up your data before any upgrade. Unless specifically noted, TeamCity does not support downgrade between major releases (changes in the first two numbers of the version). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |