Child pages
  • TeamCity Shared Resources

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


This plugin allows to limit

the number of
concurrently running builds from different build configurations based on defined hidden-data "resources" and "locks".
Current version supports multiple read and write locks per build configuration.


Install the plugin as usual.

Managing resources

Resource is a named entity that is defined per project. Build configurations can lock resources during execution of build steps. To create a resource, head to project configuration page. There choose 'SharedResources' tab.
Resources can have quota - maximum number of concurrent read locks. Example below shows two resources: one with quota, one without.

Image Added

Managing locks

There are two types of locks supported: read locks and write locks. Read locks are shared (multiple builds with read locks are allowed), write locks are exclusive (only a single running build with a write lock is allowed).

  • After installing the pluginTo add a lock, head to a build step stem in a your build configuration, that requires locks.
  • Add a build feature 'Shared Resources management'
    • Image RemovedImage Added
  • Use dialog to add necessary locks
  • Save your changes. Locks will be visible on the build step page
    • Image Removed
  • If you want to define additional resources, you can do it in-place
    • Image Added

Information in build queue

  • To see locks in effect, see builds standing in head to build queue page. Screenshot below shows a build waiting fo lock
TODO: add description of build parameters defined