Downloads of v 2019.1-EAP4:


Last Update:

03 Apr 2019

Package Maintainer(s):

Software Author(s):

  • JetBrains


jetbrains developer admin visualstudio teamcity

JetBrains TeamCity Add-in

This is a prerelease version of JetBrains TeamCity Add-in.

2019.1-EAP4 | Updated: 03 Apr 2019



Downloads of v 2019.1-EAP4:



Software Author(s):

  • JetBrains

JetBrains TeamCity Add-in 2019.1-EAP4

This is a prerelease version of JetBrains TeamCity Add-in.

This Package Contains an Exempted Check

1 Test Passing and 1 Exempted Test

Validation Testing Passed

Verification Testing Exempt:

.NET 4.6.1 dependency requiring reboot

To install JetBrains TeamCity Add-in, run the following command from the command line or from PowerShell:


To upgrade JetBrains TeamCity Add-in, run the following command from the command line or from PowerShell:


To uninstall JetBrains TeamCity Add-in, run the following command from the command line or from PowerShell:


NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to

4. Choose your deployment method:

choco upgrade teamcityaddin -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:

choco upgrade teamcityaddin -y --source="'STEP 3 URL'"

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0

Exit $exitCode

- name: Ensure teamcityaddin installed
    name: teamcityaddin
    state: present
    version: 2019.1-EAP4
    source: STEP 3 URL

See docs at

Coming early 2020! Central Managment Reporting available now! More information...

chocolatey_package 'teamcityaddin' do
  action    :install
  version  '2019.1-EAP4'
  source   'STEP 3 URL'

See docs at

    Name: teamcityaddin,
    Version: 2019.1-EAP4,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller teamcityaddin
   Name     = 'teamcityaddin'
   Ensure   = 'Present'
   Version  = '2019.1-EAP4'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'teamcityaddin':
  provider => 'chocolatey',
  ensure   => '2019.1-EAP4',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install teamcityaddin version="2019.1-EAP4" source="STEP 3 URL"

See docs at

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved as a trusted package on 03 Apr 2019.


If you use TeamCity continuous integration server to build and test your Visual Studio projects, TeamCity Add-in can help you access, execute, and analyze builds and tests on your TeamCity server without leaving Visual Studio.

You can get the most from TeamCity Add-in when working with centralized version control systems (VCS) (like Perforce, Subversion, or Team Foundation Server), where light feature branches are not a part of the workflow. For these VCSs, TeamCity Add-in provides the possibility to run personal builds so that you can test your local changes on your TeamCity server before you commit them to your VCS.

The TeamCity Add-in is a free Visual Studio extension that seamlessly integrates with Visual Studio 2010, 2012, 2013, 2015, and 2017 and with other JetBrains .NET tools such as ReSharper and dotCover.

$platformPackageName = 'resharper-platform'
$packageName = 'teamCityAddin'
$scriptPath = $(Split-Path -parent $MyInvocation.MyCommand.Definition)
$commonPath = $(Split-Path -parent $(Split-Path -parent $scriptPath))
$filename = 'JetBrains.ReSharperUltimate.2019.1.EAP4.Checked.exe'

$installPath = Join-Path  (Join-Path $commonPath $platformPackageName) $filename
$packageArgs = @{
  packageName   = $packageName
  fileType      = 'exe'
  file          = $installPath
  silentArgs    = "/Silent=True /SpecificProductNames=teamCityAddin /VsVersion=*"
  validExitCodes= @(0)
  softwareName  = 'TeamCity Add-in'
Install-ChocolateyInstallPackage @packageArgs
$platformPackageName = 'resharper-platform'
$packageName = 'teamCityAddin'
$scriptPath = $(Split-Path -parent $MyInvocation.MyCommand.Definition)
$commonPath = $(Split-Path -parent $(Split-Path -parent $scriptPath))
$filename = 'JetBrains.ReSharperUltimate.2019.1.EAP4.Checked.exe'

$installPath = Join-Path  (Join-Path $commonPath $platformPackageName) $filename
Uninstall-ChocolateyPackage $packageName 'exe' '/Silent=True /SpecificProductNamesToRemove=teamCityAddin /VsVersion=*' $installPath

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status
JetBrains TeamCity Add-in 2020.3-EAP5 2 Friday, October 30, 2020 Approved
JetBrains TeamCity Add-in 2020.3-EAP4 7 Saturday, October 17, 2020 Approved
JetBrains TeamCity Add-in 2020.3-EAP3 8 Friday, October 9, 2020 Approved
JetBrains TeamCity Add-in 2020.3-EAP2 8 Friday, October 2, 2020 Approved
JetBrains TeamCity Add-in 2020.3-EAP1 11 Friday, September 25, 2020 Approved
JetBrains TeamCity Add-in 2020.2.3 18 Saturday, September 19, 2020 Approved
JetBrains TeamCity Add-in 2020.2.2 17 Friday, September 11, 2020 Approved
JetBrains TeamCity Add-in 2020.2.1 28 Saturday, August 22, 2020 Approved
JetBrains TeamCity Add-in 2020.2 25 Thursday, August 13, 2020 Approved

Discussion for the JetBrains TeamCity Add-in Package

Ground Rules:

  • This discussion is only about JetBrains TeamCity Add-in and the JetBrains TeamCity Add-in package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or JetBrains TeamCity Add-in, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus