22 plugins in category «Extended Settings for Build Configurations»

Agent priority

Plugin for ordering TeamCity build agents. This plugin gives you a possibility to prioritize your build agents by different criteria, so whenever the build starts, available agent with higher weight will be used. So far, you can prioritize by:
  • By build status: this priority would sort agents depending on the build result, that was received during previous executions
  • By configuration parameter: this priority would sort agents by the given parameter, provided by user. Parameter should be set in buildAgent.properties file
  • By CPU benchmark index: this priority would sort agents by CPU benchmark index, calculated during agent start
  • By name: this priority would sort agents by name
Each priority could have some parameters, which are described on the corresponding configuration page. Multiple priorities could be selected and reordered. For your convenience, there is a possibility to check prioritization: select the build for which you would like to see ordered agent and you would see agents in sorted order.


[plugin by JetBrains]
allows you to share the sequence of build numbers among several build configurations


[plugin contest 2015 participant]
automatic builds triggering by bisecting changes to find the breaking change

Build messages highlighter

[plugin contest 2015 participant]
- Allows highlighting the key info for a build on the Build Overview page using TeamCity service messages.

Chuck Norris

[plugin contest 2015 participant]
Inspired by Jenkins Chuck Norris plugin ( https://wiki.jenkins-ci.org/display/JENKINS/ChuckNorris+Plugin)

Date Build Number

adds a date to the build number. See also Groovy plug and "Formatted Date Parameter" below.

Failure Formula

a custom metric which can be used to fail a build if it runs certain percentage longer than the previous one.

Formatted Date Parameter

provides a configuration parameter with the current date/timestamp.

Git Scheduling Trigger

a custom implementation for TW-23879:Ability to trigger builds in specific branches by schedule

Kill Billd

Kills Bill builds running for too long comparing to last successful build

Matrix Build

build runner to trigger a matrix build in another build configuration and report the summary of the results on a build tab


publishing build artifacts to a network share (server-side)

Octopus Deploy Build Trigger plugin

A TeamCity plugin that polls Octopus Deploy, and triggers a TeamCity build when:
  • a deployment to an environment is complete
  • a successful deployment to an environment is complete
  • a release is created
  • a new tentacle is added
  • the release process for a project is changed
NOTE: This plugin was written before Octopus subscriptions was released. This plugin polls the Octopus server and therefore puts extra load on it. If possible, you should aim to use subscriptions and web-hooks if possible.


[plugin by JetBrains]
Adds the ability to run builds in sandboxes, under different user accounts (requires TeamCity 6.5.3)

Shared Build Number

provides build number sharing among build configurations and more.

Shared Resources

By orybak
[plugin by JetBrains]
(bundled since TeamCity 8.0) allows you to limit concurrently running builds from different build configurations based on defined "resources" and "locks".


[plugin by JetBrains]
cleaning checkout directory (deleting new files) after the build (bundled since TeamCity 5.1)

Tag build

service message to add a tag for the current build

TeamCity-Gerrit Build Trigger plugin

allows setting up a build trigger in TeamCity for a new Gerrit patch set


Issues unique build numbers to builds across projects in a simple counter fashion. See also the Autoincrementer plugin above.

Url Build Trigger

[plugin by JetBrains]
Adds a build to the build queue when detecting a change in the specified URL.

Web parameters

Web-parameters is plugin for JetBrains Teamcity server, that extends default dropdown box with parameters populated from web service. With this plugin you can make your builds more flexible, as your parameters would be populated on fly. For example, you can fetch options from

  • database query
  • VCS listing (folder, tag)
  • LDAP
  • name your own
Here are some highlights of a plugin:
  • dynamic values from external web-service
  • url can use values from other parameters
  • supports images
  • possibility to configure single/multi select
  • tag support (user can add his own value)