Child pages
  • Migration Guide
Skip to end of metadata
Go to start of metadata

This document provides guidelines to migrate your projects from TeamCity TestDrive to your on-premises installation.


To do this, perform the following:


Install and Start TeamCity On-Premises

Install and start the TeamCity server with the default database.


Download TeamCity

Download TeamCity to install the free Professional Edition, the full-featured TeamCity bundled with 3 build agents with a limit of 100 build configurations since TeamCity 2017.2 (20 in earlier versions). After evaluation, you can switch to the Enterprise edition: Licensing Policy provides details. The pricing is available on the JetBrains site.

Earlier versions are available on the Previous Releases Downloads page.

Install TeamCity

on Windows

Run the .exe file and follow the instructions of  the TeamCity Setup wizard. The TeamCity web server and one build agent will be installed on the same machine.
(warning) 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 directory 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. in the example below we've set the port to 8111.
  4. The agent port: 9090 is the default for incoming connections from the server. If the port is already in use, you'll be asked to change it by setting the ownPort property to a different value.

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 

  • To stop the server and the default agent, use 

If you did not change the default port (80) during the installation, the TeamCity web UI can be accessed via http://localhost in a web browser running on the same machine where the server is installed. Otherwise use http://localhost:<port>  (http://localhost:8111 in our case) 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. Since TeamCity 10.0, Oracle Java 1.8 JDK is required for this test installation. 
    Open a command-line terminal and run the following command:

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

  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

    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.
    (warning) 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 

  • To stop the server and the default agent, use 

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 Home>/conf/server.xml file, change the port number in the <Connector> XML node, e.g.:

 

Start TeamCity for the First Time

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 now, keep the default internal database. 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


Export your Project from TeamCity TestDrive

Next we will export the configuration files of your project to an archive to later import it to your new on-premises installation.


To export the project settings, perform the following: 

  1. Go to the project settings, from the Actions menu in the top right of the project settings page select Export Project...:

  2. The Settings Export page is displayed allowing exporting the project and viewing all its dependencies. Click Export to download a zip archive containing project settings.



Import your Project to TeamCity On-Premises

In your TeamCity on-premises installation:

Go to the Server Administration area and select Project Import on the left. Upload your project settings and follow the wizard. When the import finishes, TeamCity will display the results.

Your project has been created on your TeamCity installation. Add it to the Overview and start running builds the same way your were doing it on TeamCity TestDrive.

  

Next Steps

 

Learn about administering TeamCity, including:

 

TeamCity Data Backup
TeamCity Configuration and Maintenance
Migrating to an External Database
Managing User Accounts, Groups and Permissions
Managing Licenses
Integrating TeamCity with Other Tools




  • No labels