Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 246 Next »

Publicly available plugins for JetBrians TeamCity

These plugins are provided on "as is" basis, no warranties, etc.
JetBrains does not endorse or recommend the plugins provided by third parties.
Mentioned third-party plugins functionality, bugs possible data loss, etc. are not responsibility of JetBrains.

Plugins provided by JetBrains are marked with icon.

The plugins are listed in the following sections:

Version Control Systems Support

Testing Frameworks Support

Notification/Visualizers

Apps, Notification and Interaction Applications

iOS

Android

Windows Phone

Misc

Issue Trackers

Troubleshooting

Remote APIs

Reporting

Administration Tools

  • Agent Tasks - enable/disable (and more) predefined set of agents by schedule
  • Configuration TFS backup - a separate .Net application that monitors TeamCity server configuration files and can automatically check the changes into TFS
  • Data Directory Browse - Adds "Browse Data Directory" under Diagnostics to allow TeamCity data directory browsing and files editing. (build)
  • TeamCity Console - Web console to run Groovy scripts in TeamCity environment. Also provides a report of server Spring context.
  • VCS Root Manager - allows to change checkout rules via remote API (announcement). TeamCity 7.0 provides the ability via REST API
  • VCS users syncronization - prototype plugin to create TeamCity users based on VCS commits

Build Runners

Extended Settings for Build Configurations

  • Autoincrementer - allows to share the sequence of build numbers between several build configurations
  • Date Build Number - adds date to build number. See also Groovy plug.
  • Git Scheduling Trigger - a custom implementation for TW-23879:Ability to trigger builds in specific branches by schedule
  • NetPublisher - publishing build artifacts to a network share (server-side)
  • RunAs - Adds ability to run builds in sandboxes, under different user accounts (requires TeamCity 6.5.3)
  • Shared Build Number - provides build number sharing between the build configurations and more.
  • Swabra - cleaning checkout directory (deleting new files) after the build (bundled since TeamCity 5.1)
  • unique - Issues unique build numbers to builds across projects in a simple counter fashion. See also Autoincrementer plugin above.
  • Url Build Trigger - Adds build to the build queue when detecting change at the specified URL.
  • TeamCity Shared Resources - Plugin allows to limit concurrently running builds from different build configurations based on defined "resources" and "locks".

Other Systems Support

Miscellaneous

Support for TeamCity in Other Tools

  • Confluence Plugin - TeamCity Integration Plugin plugin for Atlassian Confluence by StiltSoft
  • github has a service hook to trigger a build in TeamCity on commit (see code at code)
  • Gradle about - a plugin for Gradle with support for TeamCity. Generates a textual description of the artifacts
  • hubot teamcity.coffee - support for some TeamCity commands for Hubot
  • Jira plugin - display TeamCity builds information in Jira issues and Dashboard. Jira plugin by StiltSoft
  • Karma - supports reporting of tests progress using TeamCity service messages
  • Maven about - a plugin for Maven with support for TeamCity. Generates a textual description of the artifacts
  • Mocha - on-the-fly reporting via service messages for Mocha JavaScript testing framework. Related post with instructions.
  • NDepend (instructions on configuring NDepend build and displaying reports in TeamCity)
  • Plastic SCM
  • QNUnit
  • uDeploy

Other Integration Examples

psake - example on reporting NUnit tests to TeamCity from psake build




Want to list your plugin? Contact us
Want to write your plugin? Read more

  • No labels