27 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.

Autoincrementer

allows you to share the sequence of build numbers among several build configurations

Azure Artifact Storage

which allows replacing the TeamCity built-in artifacts storage by Azure Blob storage. The artifacts storage can be changed at the project level. After changing the storage, new artifacts produced by the builds of this project will be published to the Azure Blob storage account. Besides publishing, the plugin also implements resolving of artifact dependencies and clean-up of build artifacts.

Bisect

automatic builds triggering by bisecting changes to find the breaking change

Build messages highlighter

- Allows highlighting the key info for a build on the Build Overview page using TeamCity service messages.

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

Google Artifact Storage

which allows replacing the TeamCity built-in artifacts storage by Google Cloud Storage. The artifacts storage can be changed at the project level. After changing the storage, new artifacts produced by the builds of this project will be published to the Google Cloud Storage bucket. Besides publishing, the plugin also implements resolving of artifact dependencies and clean-up of build artifacts.
For details please read the blog post about this plugin usage.

Gradle Build Cache

By rodm
Gradle Build Cache is a TeamCity plugin that provides a build feature to enable the Gradle Build Cache. The plugin applies the Gradle Hazelcast settings plugin to enable remote build caching and starts a Hazelcast node on the TeamCity Server.

Gradle Init Scripts

By rodm
Gradle Init Scripts is a plugin that manages Gradle initialization scripts for reuse within a project or projects. Gradle initialization scripts can be used to configure repositories, plugins and other tools when running Gradle builds in TeamCity. See the Gradle documentation on initialization scripts for possible uses.

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

NetPublisher

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.

RunAs

Adds the ability to run builds in sandboxes, under different user accounts (requires TeamCity 6.5.3)

S3 Artifact Storage

This plugin allows replacing the TeamCity built-in artifacts storage with AWS S3. The artifacts storage can be changed at the project level. After changing the storage, new artifacts produced by the builds of this project will be published to the (specified) AWS S3 bucket. Besides publishing, the plugin also implements resolving of artifact dependencies and clean-up of build artifacts.

Shared Build Number

provides build number sharing among build configurations and more.

Shared Resources

(bundled since TeamCity 8.0) allows you to limit concurrently running builds from different build configurations based on defined "resources" and "locks".

Swabra

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

unique

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

Url Build Trigger

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)