Make a note of the location of the config file as you may need to edit it at some point in the future. Note that it has been configured to look at the port number listed in the previous screen:Ĭlick "save" and you will see a confirmation dialog. Next you will be presented with the "Configure Build Agent Properties" screen. This port number is used to configure TomCat which the Java based TeamCity server will be hosted in.īy default port 80 is entered – but this port is already being used by IIS 7, so change to port number to 8080 (assuming that you do not have another service listening on that port): Once the installation has finished you will be presented with the following screen, which asks you to specify the port number that TeamCity will run on. Click next to start the installation process. We have modified the configuration directory to sit inside the installation directory rather than in the user's profile folders. The default topology allows you to configure both the CI Server and the Build Agents onto the same box – if you have a large team, who make a large number of commits – it might be advisable to scale out the Build Agents onto separate boxes. Next select all the components you want installed on your server.
#Teamcity icon install
We have modified the destination folder from the default (a Team City folder in the root of C) to install into Program Files (we are running on a 64bit server, hence the (x86)):
![teamcity icon teamcity icon](https://cdn.freebiesupply.com/logos/thumbs/2x/twix-3-logo.png)
The install experience is very straightforward, first run the installer:
![teamcity icon teamcity icon](https://www.jetbrains.com/teamcity/whatsnew/screenshots/2017.1/build_chain_icon.png)
#Teamcity icon how to
In this Step by Step Guide we will show you how to configure TeamCity to run on Windows Server 2008 R2 and proxy requests through IIS 7 so that you can access your TeamCity server via a custom domain, for example įirst download the TeamCity Windows Installer (WAR / JAR version are also available) – this is a totally self contained package that contains a pre-configured Apache TomCat instance. We've believe that the combination of a virtualised development environment and a mature Continuous Integration Platform is a powerful one, especially because TeamCity allows us to easily scale out our build capacity by adding more Build Agents that can be hosted on Azure Virtual Machines or even Amazon EC2 instances. By Howard van Rooijen Co-Founder 11th November 2010īecause we believe in working smarter, not harder, our Continuous Integration Server of choice is JetBrain's TeamCity.