![]() ![]() Enter the url of the SVN server, this is the directory which will be monitored. Given this a friendly name, and select the type for example Subversion. Next stage is setup the source control which TeamCity should monitor.Ĭlick Create and Attach new VCS root. For example, to copy everything to a buildrelease directory the syntax would be: These files could be your binaries or an installer. Next, you can enter some artifacts, these are the files which are saved and stored on the build server. Give this a friendly name, you can then enter a build number which can be used in your build scripts and on TeamCity’s UI as I described in a previous post. The next stage is to add a build configuration, this will be how the project monitors source control and what is executes to build the project.Īfter clicking Create build configuration, you will be shown the first build configuration page. You will then need to enter a friendly name for your project. You will then be shown with the homepage for the server. You will need to accept the license agreement and create an admin account. Once it has been installed, visit the webpage (for me this was localhost:8080). This will install both the server and a build agent, TeamCity allows for multiple build agents on different machines to allow you to share the load of building and running tests. Installing TeamCity is an easy process, you simply download the installer from the site and click next a few times. In this post, I thought I would explain how easy it is to setup a new TeamCity project. TeamCity is a continuous integration server, similar to CruiseControl.NET, however I find it much more useful, easy to use and more importantly easy to manage. On Tuesday I gave a 10 minute nugget at NxtGenUG Cambridge on how to setup a project using JetBrain’s TeamCity. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |