Teamcity Tutorial

Introduction Installing User management in TeamCity Group management in TeamCity Setting up the projects Creating project from scratch Creating project by URL Viewing all projects, sub-projects and builds in TeamCity Project page Configuring visible projects Project configurations General settings VCS roots Report tabs Build schedules SSH keys Clean-up rules Project actions Build Configurations General settings Version control settings of a build Build steps Adding build triggers Adding failure conditions Passing parameters to build Build Configuration actions Build configuration templates Various build steps Build steps for Gradle project Build steps for Maven project Build steps for .Net project Build steps for command line Powershell runner Duplicate code finder runner Executing Selenium tests in TeamCity Running builds Viewing the build run history Environment variables in TeamCity Pinning builds Build investigations Tagging builds Configuring and Viewing artifacts of build Setting up the build agents Enable and disable build agent View build agent summary View build history of an agent viewing build agent logs Managing compatible configurations on a build agent View build runners Viewing build agent parameters Build agent pools Tracking changes Managing Build Queue Configuraing build priorities in queue Favorite builds Personal settings and tools in TeamCity Global settings in TeamCity NuGet integration in TeamCity Viewing build time in TeamCity Viewing build disk usage in TeamCity Audit and Actions in TeamCity Authentication settings in TeamCity Email server set up in TeamCity Back up builds and projects in TeamCity Importing backup in TeamCity Viewing license information Cleaning up TeamCity server Usage statistics in TeamCity Plugins in TeamCity

Global settings in Teamcity

Global settings can be accessed from Administration page as shown in below image. These settings apply to all builds configured in the server. But you can override them in each build as well. Here is the list of important settings.
  • Server URL – You change the server url using this setting
  • Maximum build artifact size – This is used to define the maximum size of the artifact created by any build. Any artifacts larger than this size will be deleted automatically.
  • Build execution timeout – Default build timeout is 0 which means that there is no restriction on how long the build runs. But if you want any build to finish execution withing specific duration of time, you can specify that time duration here.
  • Version control settings – Version control settings allow you to specify interval after which VCS should be polled for changes. If changes are detected, build will be triggered. But before adding build into queue, TeamCity waits for the specific duration called as quiet period. If more changes are detected during quiet period, VCS changes check interval starts all over again.
Complex problems, Simple Solutions