Click the Install Build Agents link and select Zip file distribution to download the archive. Make sure a JDK 1.6+ is properly installed on the agent computer. The number of authorized agents is limited by the number of agents licenses on the server.
To change it, use the standard Windows Services applet (Control Panel|Administrative Tools|Services) and change the user for the TeamCity Build Agent service. By default, the agent’s property is not configured; when the agent first connects to the server, it receives it from the TeamCity server. To change the protocol for an individual agent after the initial agent configuration, change the value of the teamcity.agent.communicationProtocols property in the agent’s properties. The agent’s property overrides the server property. After the change the agent will restart automatically upon finishing a running build, if any.
How to Add a Build Report Tab
If you have a lot of projects or build configurations, we recommend you avoid using the Default agent in order to free up the TeamCity server resources. The TeamCity Administrator can disablethe default agent on the Agents page of the web UI. Run the \bin\service.install.bat script under a user with sufficient privileges to register the new agent service.
- If they are not, you can change them via web UI.
- The Windows uninstaller is not updated during the upgrade, so after several updates, old TeamCity version will still be noted in Windows lists.
- Install a required Java on the agent into one of the standard locations, and restart the agent – the agent should then detect it and provide an action to use a newer Java in the web UI .
- Start the script without parameters to see the usage instructions.
- The set of parent projects is to be identified manually based on the web UI or the directory names on disk .
If you want the users to accept a special agreement before using your TeamCity instance, you can install a dedicated plugin developed by JetBrains for this purpose. Refer to the plugin’s documentation for more details. When you want to delete personal data of a specific user, the best way to do it is to delete the user in TeamCity. This way all the references to the user will continue to store the numeric user id, while all the other user information will not be stored anymore.
Watch Several TeamCity Servers with Windows Tray Notifier
It does not make sense to switch to 64 bit if you dedicate less than the double amount of memory to the application. The 32-bit JVM can reliably work with up to 1Gb heap memory (-Xmx1024m). It’s highly unlikely that you will need to dedicate more than 4Gb of memory to the TeamCity process. First we need to create a Report Tab, a Project-wide setting in TeamCity.
This can be done with database-specific tools or with the bundled maintainDB tool by backing up database data and then restoring it. See corresponding section in server installation instructions. Note that the proxy has to be configured not to cache any TeamCity server responses; for example, if you use Squid, installing and configuring teamcity service add “cache deny all” line to the squid.conf file. For configuring clients to access TeamCity server via HTTPS while using self-signed certificate, check the related instructions. For better TeamCity server performance, it is recommended to change some of the parameters of the newly installed PostgreSQL server.
Installing Several Build Agents on the Same Machine
You will need it during the new version installation. When a new version of TeamCity is detected, the server displays the corresponding health item for system administrators. The item points to the server’s Administration | Updates page, where all the versions available for the update are listed. Once newer TeamCity version changes the data format of database and Data Directory, you cannot use this data to run an older TeamCity version.
Templates from other projects which are not parents of the copied one. This configuration is actually deprecated in TeamCity 8.0 and is only supported as legacy. Templates used in several projects should be moved to the common parent project or root project. The set of parent projects is to be identified manually based on the web UI or the directory names on disk . If you copy a production server to create a test server, you need to ensure that the users and production systems are not affected. Install new agents and configure them to connect to the new server .
Set Up TeamCity behind a Proxy Server
These are stored under various files under .BuildServer\config directory and should be synchronized either on the file level or by configuring the same settings in the server administration UI. The number of required build agents depends on the server usage pattern, type of builds, team size, commitment of the team to CI process, and so on. In general, the best way is to start with three agents and see how they handle the projects on your server, and then make estimations for the future. This is not a recommended setup for production purposes because of security concerns. Moreover, the build procedure can slow down the responsiveness of the web UI and overall TeamCity server functioning.
For TeamCity agent Java requirements, check Setting up and Running Additional Build Agents. Now we have everything configured and ready to see some results. Our build configuration is scheduled run every night but we can also run it manually any time we want.
Configure TeamCity to Use Proxy Server for Outgoing Connections
It does not make sense to switch to 64-bit if you dedicate less than the double amount of memory to the application. If you install a server from .exe, you can customize the port in the installation wizard. Before installing the TeamCity server, you might want to estimate your system requirements and read about supported platforms.
Upon the new server startup, remember to update the Server URL on Administration | Global Settings page. Check that you can successfully authenticate on the https://www.globalcloudteam.com/ new server, use super user access if necessary. Ensure the original and copied servers use different Data Directories, databases, and artifact directories.
Installing via ZIP File
Switch agents to the new URL (requires updating the serverUrl property in buildAgent.properties on each agent). If you want to install agents anew but preserve agent’s name and authentication status, you can install a new agent and copy the conf\buildAgent.properties file from an old agent . The TeamCity server will now start automatically when the machine starts. To configure automatic start of a TeamCity build agent, see the dedicated section. TeamCity Server has the main process which can also launch child processes. Child processes use available memory on the machine.