Downloads:
491,771
Downloads of v 6.0.1:
14,077
Last Update:
05 Jun 2023
Package Maintainer(s):
Software Author(s):
- JetBrains
Tags:
teamcity build agent ci continuous integration admin- Software Specific:
- Software Site
- Software License
- Software Docs
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
TeamCity Build Agent
- 1
- 2
- 3
6.0.1 | Updated: 05 Jun 2023
- Software Specific:
- Software Site
- Software License
- Software Docs
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Downloads:
491,771
Downloads of v 6.0.1:
14,077
Software Author(s):
- JetBrains
TeamCity Build Agent 6.0.1
Legal Disclaimer: Neither this package nor Chocolatey Software, Inc. are affiliated with or endorsed by JetBrains. The inclusion of JetBrains trademark(s), if any, upon this webpage is solely to identify JetBrains goods or services and not for commercial purposes.
- 1
- 2
- 3
This Package Contains an Exempted Check
Not All Tests Have Passed
Deployment Method: Individual Install, Upgrade, & Uninstall
To install TeamCity Build Agent, run the following command from the command line or from PowerShell:
To upgrade TeamCity Build Agent, run the following command from the command line or from PowerShell:
To uninstall TeamCity Build Agent, run the following command from the command line or from PowerShell:
Deployment Method:
This applies to both open source and commercial editions of Chocolatey.
1. Enter Your Internal Repository Url
(this should look similar to https://community.chocolatey.org/api/v2/)
2. Setup Your Environment
1. Ensure you are set for organizational deployment
Please see the organizational deployment guide
2. Get the package into your environment
Option 1: Cached Package (Unreliable, Requires Internet - Same As Community)-
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
-
Open Source
-
Download the package:
Download - Follow manual internalization instructions
-
-
Package Internalizer (C4B)
-
Run: (additional options)
choco download teamcityagent --internalize --source=https://community.chocolatey.org/api/v2/
-
For package and dependencies run:
choco push --source="'INTERNAL REPO URL'"
- Automate package internalization
-
Run: (additional options)
3. Copy Your Script
choco upgrade teamcityagent -y --source="'INTERNAL REPO 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 teamcityagent -y --source="'INTERNAL REPO URL'"
$exitCode = $LASTEXITCODE
Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
Exit 0
}
Exit $exitCode
- name: Install teamcityagent
win_chocolatey:
name: teamcityagent
version: '6.0.1'
source: INTERNAL REPO URL
state: present
See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.
chocolatey_package 'teamcityagent' do
action :install
source 'INTERNAL REPO URL'
version '6.0.1'
end
See docs at https://docs.chef.io/resource_chocolatey_package.html.
cChocoPackageInstaller teamcityagent
{
Name = "teamcityagent"
Version = "6.0.1"
Source = "INTERNAL REPO URL"
}
Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.
package { 'teamcityagent':
ensure => '6.0.1',
provider => 'chocolatey',
source => 'INTERNAL REPO URL',
}
Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.
4. If applicable - Chocolatey configuration/installation
See infrastructure management matrix for Chocolatey configuration elements and examples.
This package was approved as a trusted package on 05 Jun 2023.
TeamCity Build Agent for jetbrains.com/teamcity. It is a piece of software which listens for the commands from the TeamCity server and starts the actual build processes. Install requires at least serverUrl parameter, e.g. -params 'serverurl=http://...', also supported are agentName, agentDir, ownPort and possibly others. If looking to see what changes in the agent config files during the run use -v argument to choco.exe.
$ErrorActionPreference = 'Stop' # stop on all errors
$toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
# Don't use ConvertFrom-StringData as it corrupts Windows paths like C:\buildAgent
function Get-PropsDictFromJavaPropsFile ($configFile) {
# Returns configProps ordered dict
$config = Get-Content $configFile
Write-Verbose "$config"
$configProps = [ordered]@{}
$config | %{if (`
(!($_.StartsWith('#')))`
-and (!($_.StartsWith(';')))`
-and (!($_.StartsWith(";")))`
-and (!($_.StartsWith('`')))`
-and (($_.Contains('=')))){
$props = @()
$props = $_.split('=',2)
Write-Verbose "Props are $props"
$configProps.add($props[0],$props[1])
}
}
return $configProps
}
$installParametersFile = "$toolsDir/install-parameters.txt"
$installParameters = Get-PropsDictFromJavaPropsFile $installParametersFile
$installParameters.GetEnumerator() | % { "$($_.Name)=$($_.Value)" } | Write-Verbose
$agentDir = $installParameters["agentDir"]
$agentName = $installParameters["agentName"]
$agentDrive = split-path $agentDir -qualifier
$workingDirectory = Join-Path $agentDir "bin"
Start-ChocolateyProcessAsAdmin "Set-Location $workingDirectory; Start-Process -FilePath .\service.stop.bat -Wait"
Sleep 2
Start-ChocolateyProcessAsAdmin "Set-Location $workingDirectory; Start-Process -FilePath .\service.uninstall.bat -Wait"
$ErrorActionPreference = 'Stop'; # stop on all errors
$packageName = 'TeamCityAgent'
$zipFileName = 'buildAgent.zip'
$uninstalled = $false
Uninstall-ChocolateyZipPackage -PackageName $packageName `
-ZipFileName $zipFileName
$toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
# Don't use ConvertFrom-StringData as it corrupts Windows paths like C:\buildAgent
function Get-PropsDictFromJavaPropsFile ($configFile) {
# Returns configProps ordered dict
$config = Get-Content $configFile
Write-Verbose "$config"
$configProps = [ordered]@{}
$config | %{if (`
(!($_.StartsWith('#')))`
-and (!($_.StartsWith(';')))`
-and (!($_.StartsWith(";")))`
-and (!($_.StartsWith('`')))`
-and (($_.Contains('=')))){
$props = @()
$props = $_.split('=',2)
Write-Verbose "Props are $props"
$configProps.add($props[0],$props[1])
}
}
return $configProps
}
$installParametersFile = "$toolsDir/install-parameters.txt"
$installParameters = Get-PropsDictFromJavaPropsFile $installParametersFile
$installParameters.GetEnumerator() | % { "$($_.Name)=$($_.Value)" } | Write-Verbose
$agentDir = $installParameters["agentDir"]
if (Test-Path $agentDir) {
"Removing $agentDir"
Remove-Item $agentDir -force -recurse
}
$uninstalled = $true
Log in or click on link to see number of positives.
- TeamCityAgent.6.0.1.nupkg (bba2d3922307) - ## / 62
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.
Add to Builder | Version | Downloads | Last Updated | Status |
---|---|---|---|---|
TeamCity Build Agent 6.0.1 | 14077 | Monday, June 5, 2023 | Approved | |
TeamCity Build Agent 5.0.3 | 64243 | Friday, November 13, 2020 | Approved | |
TeamCity Build Agent 5.0.2 | 887 | Wednesday, November 11, 2020 | Approved | |
TeamCity Build Agent 5.0.1 | 338 | Tuesday, November 10, 2020 | Approved | |
TeamCity Build Agent 5.0.0 | 171 | Tuesday, November 10, 2020 | Approved | |
TeamCity Build Agent 4.1.0 | 16912 | Tuesday, July 14, 2020 | Approved | |
TeamCity Build Agent 4.1.0-beta-2 | 249 | Thursday, June 18, 2020 | Approved | |
TeamCity Build Agent 4.1.0-beta-1 | 222 | Monday, May 18, 2020 | Approved | |
TeamCity Build Agent 4.0.2 | 55708 | Thursday, November 28, 2019 | Approved | |
TeamCity Build Agent 4.0.1 | 191 | Thursday, November 28, 2019 | Approved | |
TeamCity Build Agent 4.0.0 | 28787 | Wednesday, June 12, 2019 | Approved | |
TeamCity Build Agent 3.0.1 | 6949 | Tuesday, January 22, 2019 | Approved | |
TeamCity Build Agent 3.0.0 | 8795 | Thursday, January 17, 2019 | Approved | |
TeamCity Build Agent 3.0.0-beta-2 | 279 | Thursday, January 17, 2019 | Approved | |
TeamCity Build Agent 3.0.0-beta-1 | 278 | Thursday, January 17, 2019 | Approved | |
TeamCity Build Agent 2.3.0-beta-1 | 404 | Wednesday, July 11, 2018 | Approved | |
TeamCity Build Agent 2.2.1 | 203857 | Friday, April 13, 2018 | Approved | |
TeamCity Build Agent 2.1.2 | 19861 | Thursday, October 19, 2017 | Approved | |
TeamCity Build Agent 2.1.1 | 12416 | Tuesday, August 1, 2017 | Approved | |
TeamCity Build Agent 2.1.0 | 414 | Wednesday, July 19, 2017 | Approved | |
TeamCity Build Agent 2.0.1-beta-12 | 444 | Wednesday, July 19, 2017 | Exempted | |
TeamCity Build Agent 2.0.1-beta-11 | 538 | Friday, March 3, 2017 | Exempted | |
TeamCity Build Agent 2.0.1-beta-10 | 474 | Thursday, March 2, 2017 | Exempted | |
TeamCity Build Agent 2.0.1-beta-09 | 461 | Wednesday, March 1, 2017 | Exempted | |
TeamCity Build Agent 2.0.1-beta-08 | 437 | Wednesday, March 1, 2017 | Exempted | |
TeamCity Build Agent 2.0.1-beta-07 | 457 | Tuesday, February 28, 2017 | Exempted | |
TeamCity Build Agent 2.0.1-beta-06 | 524 | Friday, January 13, 2017 | Exempted | |
TeamCity Build Agent 2.0.1-beta-05 | 704 | Friday, November 4, 2016 | Exempted | |
TeamCity Build Agent 2.0.1-beta-04 | 500 | Thursday, November 3, 2016 | Exempted | |
TeamCity Build Agent 2.0.1-beta-03 | 524 | Friday, October 28, 2016 | Exempted | |
TeamCity Build Agent 2.0.1-beta-02 | 533 | Tuesday, October 18, 2016 | Exempted | |
TeamCity Build Agent 2.0.1-beta-01 | 489 | Monday, October 17, 2016 | Exempted | |
TeamCity Build Agent 2.0.0 | 34396 | Friday, October 14, 2016 | Approved | |
TeamCity Build Agent 1.2.1 | 523 | Friday, October 14, 2016 | Approved | |
TeamCity Build Agent 1.2.0 | 664 | Friday, October 14, 2016 | Approved | |
TeamCity Build Agent 1.1.0 | 9067 | Tuesday, December 9, 2014 | Approved | |
TeamCity Build Agent 1.0.9 | 640 | Monday, September 29, 2014 | Approved | |
TeamCity Build Agent 1.0.8 | 520 | Monday, September 29, 2014 | Approved | |
TeamCity Build Agent 1.0.7 | 534 | Monday, September 29, 2014 | Approved | |
TeamCity Build Agent 1.0.6 | 610 | Thursday, July 3, 2014 | Approved | |
TeamCity Build Agent 1.0.5 | 845 | Thursday, March 13, 2014 | Approved | |
TeamCity Build Agent 1.0.4 | 587 | Wednesday, March 12, 2014 | Approved | |
TeamCity Build Agent 1.0.3 | 610 | Wednesday, March 12, 2014 | Approved | |
TeamCity Build Agent 1.0.2 | 533 | Tuesday, March 11, 2014 | Approved | |
TeamCity Build Agent 1.0.1 | 483 | Wednesday, March 5, 2014 | Approved | |
TeamCity Build Agent 1.0.0 | 616 | Thursday, February 20, 2014 | Approved |
JetBrains s.r.o.
Version 3.x of this package uses AdoptOpenJDK. Version 4.x depends on Chocolatey 0.10.14.
-
- corretto11jdk (≥ 11.0.19)
Ground Rules:
- This discussion is only about TeamCity Build Agent and the TeamCity Build Agent 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 Build Agent, 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.