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

Managing build queue in Teamcity

We can have multiple build agents in TeamCity. So multiple builds can be run simultaneously on different agents. But sometimes, build agents are not enough to run the builds because at a time one agent runs only one build. In this scenario, if you try to run extra build, that build is put in the build queue. Whenever the compatible agent is free, that build is assigned to that agent automatically. Below image shows how the build queue looks like in TeamCity.Builds are picked from queue in ascending order to run. For example – in above image, build with id #1 will be run before build with id #2. From build queue page, you can do below things.
  • View all builds that are in the queue and also view who triggered it and expected time to start
  • Configure build priorities
  • Pause and resume build queue
  • Remove specific build from the queue
  • It also shows the name of agent on which specific build can run
  • We can also reorder the position of the builds which helps us to run specific build early or delay it’s execution
Complex problems, Simple Solutions