Create a backup. Note the username used to run the TeamCity server. You will need it during the new version installation. If you have any of the Windows service settings customized, store them to repeat the customizations later. Check if you a have local agent installed though it is not recommended to have a local agent , so that you can later select this option in the installer.
Run the new installer and point it to the same place TeamCity is installed to the location used for installation is remembered automatically. Confirm uninstalling the previous installation.
The TeamCity uninstaller ensures proper uninstallation, but you might want to make sure the TeamCity server installation directory does not contain any non-customized files after uninstallation finishes. Check and restore any customizations of Windows services and Tomcat configuration that you need.
When upgrading from TeamCity versions 7. It is recommended to copy the. Review the TeamCity Maintenance Mode page to make sure there are no problems encountered, and confirm the upgrade by clicking the corresponding button.
Only after that all data will be converted to the newer format. It's advised to back up the directory beforehand. If you use a Tomcat server your own or bundled in. Note that this may affect other web applications deployed into the same web server.
Restore customized settings backed up in step 2 above. Make sure the previously configured TeamCity server startup properties if any are still actual. Only after that, all the configuration data and database scheme are updated by TeamCity converters.
If you made no changes to the container, you can just stop the running container, pull the new version of the official TeamCity image and the server in it via the usual command.
If you changed the image, you will need to replicate the changes to the new TeamCity server image. It is recommended for all users to regularly update their IDE plugins to the latest version compatible with the TeamCity server version in use — at least to the version available from the TeamCity server's Tools section in the user profile.
Users with non-matching plugin versions get a message on an attempt to log in to the TeamCity server with a non-matching version. On starting the TeamCity server and updating agent distributions or plugins on the server , TeamCity agents connected to the server and correctly installed are automatically updated to the version corresponding to the server.
This occurs for both server upgrades and downgrades. If there is a running build on the agent, the build finishes. No new builds are started on the agent unless the agent is up to date with the server. Before starting the agent upgrade, the agent is checked for free disk space, 3 GB by default.
To modify the value required for the upgrade, configure the teamcity. The agent update procedure is as follows: The agent agent. However, in PowerShell is a comment so you must enclose the statement in double quotes. This demo breaks down querying the Star Wars api into different build steps just to demonstrate the passing of parameters you could easily do this in one step!
As noted in the TeamCity documents, the modified values of the parameters will be available in the build steps that follow if you need to use them in the current build step, assign them to a variable in that script before using that variable to set the system message value. Here are the general build settings for each step. Being able to set and pass parameters between build steps in TeamCity is really useful and makes the builds much more flexible.
This example showed how to do so using Source Code entered directly in the script block for PowerShell and there is a slightly different technique if it is PowerShell scripts that need to use the input parameters. View this page in the latest documentation or refer to the listing to choose the documentation corresponding to your TeamCity version. It is strongly recommended to back up your data before any upgrade. TeamCity supports upgrades from any of the previous versions to the later ones.
All the settings and data are preserved unless noted in the Upgrade Notes. If you plan to upgrade a production TeamCity installation, it is recommended to install a test server and check its functioning in your environment before upgrading the main one. Before upgrade, please make sure the maintenance period of your licenses is not yet elapsed use Administration Licenses TeamCity server web UI page to list your license keys.
The licenses are valid only for the versions of TeamCity with the effective release date within the maintenance period. See the effective release date at the page.
Please note that the licensing policy in TeamCity versions 5. Review the Licensing Policy page and the Licensing and Upgrade section on the official site. If you are evaluating a newer version, you can get an evaluation license on the download page.
Please note that each TeamCity version can be evaluated only once. To extend the evaluation period, contact JetBrains sales department. TeamCity supports upgrades from any of the previous versions to the current one. Unless specifically noted, downgrades with preserving the data are not possible with changing major. The general policy is that bugfix updates changes in the Z part of X. However, when upgrading to the next major or minor version changed X or Y in X. Z TeamCity version , you will not be able to downgrade with the data preservation: you will need to restore a backup of the appropriate version.
Unfortunately because of bugs in Apache Portable Runtime , TeamCity may not work properly in this case. If you want to use another version of Tomcat web server instead of the bundled one, you have the choices of whether to use the. For the latter, you might want to:. Upon successful installation, the TeamCity server web UI can be accessed via a web browser.
The default address that can be used to access TeamCity from the same machine depends on the installation package and installation options. Port 80 is used for Windows installation, unless another port is specified, port for. One of the most common issues with the server installation is using a port that is already used by another program. If you use the TeamCity server Windows installer, you can set the port to be used during installation.
If you use the. Use the following instructions to change the port if you use the. If another application uses the same port as the TeamCity server, the TeamCity server Tomcat server won't start and this will be identified by "Address already in use" errors in the server logs or server console. TeamCity both server and agent requires JRE 1. It is recommended to use 32 bit installation unless you need to dedicate more memory to TeamCity server.
Please check 64 bit Java notes before upgrade. Note that on upgrade, TeamCity will overwrite the existing JRE with the bundled bit version, so you'll have to update to the bit JRE again after upgrade. TeamCity server can run under both the and bit JVM. It is recommended to use the bit JVM unless you need to dedicate more than 1.
0コメント