![]() Navigate up to your server node, and double click the "URL Rewrite" icon under the "IIS" section Navigate up to the "Server Farms" node in the "Connections" pane – you should see that TeamCity is now listed as a Server Farm: IIS will ask if you want it to create a URL rewrite rule. Now update the httpPort to the number entered during the installation process – in our case this is 8080, click "Finish" once done: Now enter the IP address of the server to allow IIS to resolve to localhost: Next, you will be prompted to add a server to the server farm: Next, enter a new Server Farm Name – call it "TeamCity", then click Next: Right click on this node and select "Create Server Farm" from the context menu: You should see a new node called "Server Farms": When this completes you will be shown a confirmation screen listing all the components that were installed: The Web Platform Installer will now install the components, firstly the "Web Farm Framework 1.0": Click "I Accept" to download and install them: The next screen will show all the required dependencies for this feature. Select the "Application Request Routing 2.1" option and click "Install": Then click "Customize" on the "Host, deliver and Scale Using IIS Media Services" section: Once installed, run the application and navigate to the Media Platform tab. If you don't already have this installed on your server – you can download it from here. The easiest way to configure IIS is via the wonderful Web Platform Installer. Now that TeamCity is successfully installed and configured we need to configure IIS to proxy web requests from port 80 to TomCat which is listening on port 8080. In the following screen I have modified the default settings to prevent public registration – thus the only option when visiting the root of the TeamCity web app is to authenticate: Note that TeamCity is only available to be resolved via localhost:8080. ![]() once you have done this you should be prompted to log-in. TeamCity will now initialise and ask you to create an administrator account and configure a database. When you click "Finish" you will be taken to the new TeamCity instance. Next you will be asked which services you wish to start immediately: Next you will be presented with a screen that asks which Windows Account you wish to run the service under. ![]() 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. 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)): The install experience is very straightforward, first run the installer: 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.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |