TeamCity

Contains actions to get artifacts and trigger builds in TeamCity.

  • About
  • Release Notes
  • Version History
  • Installation

Scale beyond simple build and deploy

Expand and standardize process by joining Continuous Integration with Application Release Automation for a well defined DevOps toolchain.

Run through the TeamCity BuildMaster tutorial to see how easy it is to integrating your CI engine with BuildMaster.

By installing the TeamCity extension in BuildMaster, you are provided with built-in TeamCity deployment plan operations. These built-in operation including:

  • Importing an artifact from TeamCity - Downloads an artifact from the specified TeamCity server and saves it to the artifact library
  • Queue a TeamCity Build - Queues a build in TeamCity, optionally waiting for its completion
  • Get Latest - Get latest version of code from TeamCity
BuildMaster intgrates with Jenkins

5.4.2

10/21/2016 3:33:37 PM
  • 25 - FIX: Error trying to queue build for default branch

5.4.1

9/30/2016 8:41:08 PM
No notes for this release

5.4.0

9/23/2016 10:42:48 PM
  • 26 - BuildMaster 5.4 Changes and TeamCity Build Number Dynamic Variable

5.2.1

8/11/2016 3:20:55 PM
No notes for this release

5.2.0

7/11/2016 3:49:27 PM
No notes for this release

5.1.0

6/17/2016 9:03:14 PM
No notes for this release

5.0.1

6/14/2016 4:00:38 PM
No notes for this release

5.0.0

4/29/2016 5:51:20 PM
No notes for this release

4.8

1/26/2016 7:42:15 PM
  • 17 - Temp file is not deleted from disk after importing build artifact

4.7

1/11/2016 4:58:40 PM
No notes for this release

4.6

7/16/2015 6:13:28 PM
  • 15 - Extension configuration dropdown does not change context on editor when a non-default option is selected
  • 14 - Importer should not assume that all non-integer values for a build number represent a special build number like "lastSuccessful"

4.5

6/26/2015 12:31:33 AM
  • 3 - Support for branches in build action

4.4

2/19/2015 9:08:18 PM
  • 11 - Enforce Build Configuration ID when creating a Build Importer Template
  • 10 - Support for TeamCity variables in artifact names

4.3

8/8/2014 11:08:07 PM
  • 9 - Implement build import capability for TeamCity
  • 5 - Set BuildMaster releaseNumber and buildNumber from TeamCity
  • 4 - Keep track of TeamCity build number for a release

4.2

11/21/2013 7:58:44 PM
  • 1 - Update for 4.0.7 compatibility and fix new styled dropdowns

4.1

10/12/2013 12:07:09 AM
No notes for this release

4.0

10/7/2013 11:57:13 PM
No notes for this release

3.1

1/18/2013 11:54:01 PM
No notes for this release

3.0

8/1/2012 4:44:46 PM
  • BMXTEAMCITY-1 - Create a Trigger Build action and a Get Artifact action
VersionReleasedRequires Version
5.4.210/21/2016BuildMaster 5.4.0download
5.4.19/30/2016BuildMaster 5.4.0download
5.4.09/23/2016BuildMaster 5.4.0download
5.2.18/11/2016BuildMaster 5.2.0download
5.2.07/11/2016BuildMaster 5.2.0download
5.1.06/17/2016BuildMaster 5.1.0download
5.0.16/14/2016BuildMaster 5.0.0download
5.0.04/29/2016BuildMaster 5.0.0download
4.81/26/2016BuildMaster 4.9.5download
4.71/11/2016BuildMaster 4.9.5download
4.67/16/2015BuildMaster 4.4.1download
4.56/26/2015BuildMaster 4.4.1download
4.42/19/2015BuildMaster 4.4.1download
4.38/8/2014BuildMaster 4.4.1download
4.211/21/2013BuildMaster 4.0.7download
4.110/12/2013BuildMaster 4.0.3download
4.010/7/2013BuildMaster 4.0.2download
3.11/18/2013BuildMaster 3.5.0download
3.08/1/2012BuildMaster 3.2.0download

If your installation of BuildMaster can access inedo.com, simply navigate to Admin > Extensions, and install or update extensions from the gallery.

You can also manually install the extension.

  1. Copy the extension file (TeamCity.bmx) to the Extension Library path (by default, this is c:\BuildMaster\Extensions).
  2. Restart the BuildMaster Service (Admin > Service).
  3. Restart the BuildMaster Web Application (Admin > All Settings > Save).
  4. Verify that the new extension has been loaded (Admin > Extensions)