Installation Quick Start

This page covers the evaluation setup of a TeamCity server with a default build agent running on the same machine for the most popular operating systems.

Note that for production purposes it is recommended to set up the TeamCity server and Agent on separate machines .

Download TeamCity

Download TeamCity to install the free Professional Edition, the full-featured TeamCity bundled with 3 build agents with a limitation of 20 build configurations will be installed. After evaluation, you can switch to the Enterprise edition: Licensing Policy provides details. The pricing is available on the JetBrains site.

https://www.jetbrains.com/teamcity/download/

Earlier versions are available on the Previous Releases Downloads page.

Install and Start TeamCity

on Windows

Run the .exe file and follow the instructions of the TeamCity Setup wizard. T he TeamCity web server and one build agent will be installed on the same machine. Note that for production purposes it is recommended to set up the TeamCity server and Agent on separate machines.

During installation, you can configure the following:

1. The TeamCity home where TeamCity will be installed.

2. Whether the TeamCity server and agent will run as Windows services.

   

3. The server port: 80 is the default port, which can be already used by other applications (e.g. Skype). Change the server port if it is already in use.

4. The agent port: 9090 is the default for incoming connections from the server. Change the ownPort property if the default port is already in use.

If the TeamCity server is installed as a Windows service, follow the usual procedure of starting and stopping services.

Otherwise, to start/stop the TeamCity server and one default agent at the same time , use the runAll script, provided in the < TeamCity home>/bin directory, e.g.

• To start the server and the default agent, use

  runAll.bat start

• To stop the server and the default agent, use

  runAll.bat stop

If you did not change the default port (80) during the installation, the TeamCity web UI can be accessed viahttp://localhost in a web browser running on the same machine where the server is installed. Otherwise use http://localhost:<port> to access the TeamCity server and build agent running on the same computer.

on Linux and OS X

1. Make sure you have JRE or JDK installed. Oracle Java 1.7 JDK, and since TeamCity 9.1 JDK 1.8, is recommended. Open a command-line terminal and run the following command:

   java -version

2. Make sure the JAVA_HOME environment variable is pointing to the Java installation directory. Run the following command in the command-line terminal:

   echo $JAVA_HOME

3. Use the TeamCity<version number>.tar.gz archive to manually install TeamCity bundled with Tomcat servlet container. Unpack the archive: e.g. under Linux use

   tar xfz TeamCity<version number>.tar.gz

   The archive can be used for installation on Windows as well.

4. The TeamCity web server and one build agent will be installed on the same machine. Note that for production purposes it is recommended to set up the TeamCity server and Agent on separate machines..

To start/stop the TeamCity server and one default agent at the same time, use the runAll script, provided in the < TeamCity home>/bin directory, e.g.

• To start the server and the default agent, use

  runAll.sh start

• To stop the server and the default agent, use

  runAll.sh stop

By default, TeamCity runs on http://localhost:8111/ and has one registered build agent that runs on the same computer. If another application uses the same port as the TeamCity server, the TeamCity server (Tomcat server) will not start with the "Address already in use" errors in the server logs or server console.

To change the server port, in the < TeamCity HomeInstallation Quick Start>/conf/server.xml file, change the port number in the <Connector> XML node, e.g.:

TeamCity First Start

On the first TeamCity start, do the following:

1. Review the location of the TeamCity Data Directory, where all the configuration information is stored. Click Proceed.

2. TeamCity stores build history, users, build results and some run time data in an SQL database and allows you to select the database type. For the purposes of evaluation, keep the default internal database. After evaluation, you will be able to switch to an external database for production use. Click Proceed.

   

   It'll take some time for TeamCity to configure the necessary components.

3. On the next screen, accept the License Agreement to proceed with the launch. Click Continue.

4. TeamCity displays the Create Administrator Account page. Specify the administrator credentials and click Create Account.

You are logged to TeamCity: now you can configure your user settings and create and run your first build.