Downloads:

33,208

Downloads of v 9.0:

330

Last Update:

12 Dec 2014

Package Maintainer(s):

Software Author(s):

  • JetBrains

Tags:

Testing Build Coding Compilation Continuous Integration CI jetbrains admin

TeamCity Add-in

This is not the latest version of TeamCity Add-in available.

  • 1
  • 2
  • 3

9.0 | Updated: 12 Dec 2014

Downloads:

33,208

Downloads of v 9.0:

330

Maintainer(s):

Software Author(s):

  • JetBrains

  • 1
  • 2
  • 3
TeamCity Add-in 9.0

This is not the latest version of TeamCity Add-in available.

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed


Validation Testing Unknown


Verification Testing Unknown


Scan Testing Successful:

No detections found in any package files

Details

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

>

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

>

To uninstall 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 https://community.chocolatey.org/api/v2. 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 https://community.chocolatey.org/api/v2)

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'"
$exitCode = $LASTEXITCODE

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

Exit $exitCode

- name: Ensure teamcityaddin installed
  win_chocolatey:
    name: teamcityaddin
    state: present
    version: 9.0
    source: STEP 3 URL

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.


chocolatey_package 'teamcityaddin' do
  action    :install
  version  '9.0'
  source   'STEP 3 URL'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


Chocolatey::Ensure-Package
(
    Name: teamcityaddin,
    Version: 9.0,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller teamcityaddin
{
   Name     = 'teamcityaddin'
   Ensure   = 'Present'
   Version  = '9.0'
   Source   = 'STEP 3 URL'
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'teamcityaddin':
  provider => 'chocolatey',
  ensure   => '9.0',
  source   => 'STEP 3 URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


salt '*' chocolatey.install teamcityaddin version="9.0" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved by moderator ferventcoder on 29 Apr 2015.

Description

The TeamCity add-in for Microsoft Visual Studio provides the following features:

Remote Run for TFS, Subversion and Perforce (for remote run for Mercurial and Git see Branch Remote Run Trigger),
Pre-Tested (Delayed) Commit for TFS, Subversion and Perforce,
fetching JetBrains dotCover coverage analysis data from the TeamCity server (see more) to MS Visual Studio (requires dotCover of the supported version installed in Visual Studio),
viewing recently committed changes and personal builds with their build status in the My Changes tool window,
opening build failure details in MS Visual Studio from the TeamCity web UI,
viewing failed tests' details for a build,
re-runing tests failed in the TeamCity build locally via the ReSharper test runner (requires ReSharper 5.0 installed),
navigation from the IDE to the build results web page,
re-applying changes sent in Remote Run or Pre-tested commit to the working directory.


tools\chocolateyInstall.ps1
$platformPackageName = 'resharper-platform'
$platformPackageVersion = '1.0'
$packageName = 'TeamCityAddin'

try {

  $scriptPath = $(Split-Path -parent $MyInvocation.MyCommand.Definition)
  $commonPath = $(Split-Path -parent $(Split-Path -parent $scriptPath))

  $installPath = Join-Path  (Join-Path $commonPath $platformPackageName'.'$platformPackageVersion) 'ReSharperAndToolsPacked01.exe'

  Start-ChocolateyProcessAsAdmin '/SpecificProductNames=TeamCityAddin /Silent=True' $installPath

  Write-ChocolateySuccess "$packageName"
} catch {
  Write-ChocolateyFailure "$packageName" "$($_.Exception.Message)"
  throw
}
tools\chocolateyUnInstall.ps1
$platformPackageName = 'resharper-platform'
$platformPackageVersion = '1.0'
$packageName = 'TeamCityAddin'

try {
  $scriptPath = $(Split-Path -parent $MyInvocation.MyCommand.Definition)
  $commonPath = $(Split-Path -parent $(Split-Path -parent $scriptPath))

  $installPath = Join-Path  (Join-Path $commonPath $platformPackageName'.'$platformPackageVersion) 'ReSharperAndToolsPacked01.exe'

  Uninstall-ChocolateyPackage packageName 'exe' '/SpecificProductNames=TeamCityAddin /HostsToRemove=dotCover01;ReSharperPlatformVs10;ReSharperPlatformVs11;ReSharperPlatformVs12;ReSharperPlatformVs14 /Hive=* /ReSharper9PlusMsi=True' $installPath

  Write-ChocolateySuccess "$packageName"
} catch {
  Write-ChocolateyFailure "$packageName" "$($_.Exception.Message)"
  throw
}

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 2021.2-EAP8 10 Friday, July 23, 2021 Approved
JetBrains TeamCity Add-in 2021.2-EAP7 12 Tuesday, July 20, 2021 Approved
JetBrains TeamCity Add-in 2021.2-EAP6 14 Saturday, July 10, 2021 Approved
JetBrains TeamCity Add-in 2021.2-EAP5 15 Friday, July 2, 2021 Approved
JetBrains TeamCity Add-in 2021.2-EAP4 19 Saturday, June 26, 2021 Approved
JetBrains TeamCity Add-in 2021.2-EAP3 13 Saturday, June 12, 2021 Approved
JetBrains TeamCity Add-in 2021.2-EAP2 23 Saturday, June 5, 2021 Approved
JetBrains TeamCity Add-in 2021.2-EAP1 15 Tuesday, June 1, 2021 Approved
JetBrains TeamCity Add-in 2021.1.4 13 Thursday, July 15, 2021 Approved
Discussion for the TeamCity Add-in Package

Ground Rules:

  • This discussion is only about TeamCity Add-in and the 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 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