Downloads:

343,199

Downloads of v 2.0.1-beta-04:

298

Last Update:

03 Nov 2016

Package Maintainer(s):

Software Author(s):

  • JetBrains

Tags:

teamcity build agent ci continuous integration

TeamCity Build Agent

This is a prerelease version of TeamCity Build Agent.

2.0.1-beta-04 | Updated: 03 Nov 2016

Downloads:

343,199

Downloads of v 2.0.1-beta-04:

298

Software Author(s):

  • JetBrains

TeamCity Build Agent 2.0.1-beta-04

This is a prerelease version of TeamCity Build Agent.

Some Checks Have Failed or Are Not Yet Complete

1 Test Passing and 1 Unknown Test


Validation Testing Passed


Verification Testing Unknown

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:

>

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

4. Choose your deployment method:


choco upgrade teamcityagent -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 teamcityagent -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 teamcityagent installed
  win_chocolatey:
    name: teamcityagent
    state: present
    version: 2.0.1-beta-04
    source: STEP 3 URL

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

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


chocolatey_package 'teamcityagent' do
  action    :install
  version  '2.0.1-beta-04'
  source   'STEP 3 URL'
end

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


Chocolatey::Ensure-Package
(
    Name: teamcityagent,
    Version: 2.0.1-beta-04,
    Source: STEP 3 URL
);

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


cChocoPackageInstaller teamcityagent
{
   Name     = 'teamcityagent'
   Ensure   = 'Present'
   Version  = '2.0.1-beta-04'
   Source   = 'STEP 3 URL'
}

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


package { 'teamcityagent':
  provider => 'chocolatey',
  ensure   => '2.0.1-beta-04',
  source   => 'STEP 3 URL',
}

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


salt '*' chocolatey.install teamcityagent version="2.0.1-beta-04" 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 is exempt from moderation. While it is likely safe for you, there is more risk involved.
Description

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.


tools\chocolateyInstall.ps1
if ($env:chocolateyPackageParameters -eq $null) {
	throw "No parameters have been passed into Chocolatey install, e.g. -params 'serverUrl=http://... agentName=... agentDir=...'"
}

$parameters = ConvertFrom-StringData -StringData $env:chocolateyPackageParameters.Replace(" ", "`n")

## Validate parameters
if ($parameters["serverUrl"] -eq $null) {
    throw "Please specify the TeamCity server URL by passing it as a parameter to Chocolatey install, e.g. -params 'serverUrl=http://...'"
}
if ($parameters["agentDir"] -eq $null) {
    $parameters["agentDir"] = "$env:SystemDrive\buildAgent"
    Write-Host No agent directory is specified. Defaulting to $parameters["agentDir"]
}
if ($parameters["agentName"] -eq $null) {
    $defaultName = $true
    $parameters["agentName"] = "$env:COMPUTERNAME"
    Write-Host No agent name is specified. Defaulting to $parameters["agentName"]
}
if ($parameters["ownPort"] -eq $null) {
    $parameters["ownPort"] = "9090"
    Write-Host No agent port is specified. Defaulting to $parameters["ownPort"]
}

## Make local variables of it
$serverUrl = $parameters["serverUrl"];
$agentDir = $parameters["agentDir"];
$agentName = $parameters["agentName"];
$ownPort = $parameters["ownPort"];
$agentDrive = split-path $agentDir -qualifier

## Temporary folder
$tempFolder = $env:TEMP

## Download from TeamCity server
Get-ChocolateyWebFile 'buildAgent.zip' "$tempFolder\buildAgent.zip" "$serverUrl/update/buildAgent.zip"

## Extract
New-Item -ItemType Directory -Force -Path $agentDir
Get-ChocolateyUnzip "$tempFolder\buildAgent.zip" $agentDir  

## Clean up
#del /Q "$tempFolder\buildAgent.zip"

# Configure agent
copy $agentDir\conf\buildAgent.dist.properties $agentDir\conf\buildAgent.properties
# ConvertFrom-StringData equivalent to longer format but loses key ordering (both strip comments)
#$buildAgentProps = convertfrom-stringdata (Get-Content $agentDir\conf\buildAgent.properties | Out-String)
$buildAgentProps = [ordered]@{}
$buildAgentConfig = get-content $agentDir\conf\buildAgent.properties
if ($ownPort -eq "9090") {
# Simply replace config elements sinnce we aren't adding any new entries
$buildAgentConfig | Foreach-Object {
    $_ -replace 'serverUrl=(?:\S+)', "serverUrl=$serverUrl" `
	   -replace 'name=(?:\S+)', "name=$agentName"
    } | Set-Content $agentDir\conf\buildAgent.properties
} else {
# Rewrite the entire config since we are adding a new element and this can be tricky to get right
# The 'if' block lines strip comments to avoid invalid/duplicate key issues
$buildAgentConfig | %{if (`
                            (!($_.StartsWith('#'))) `
                                -and (!($_.StartsWith(';')))`
                                -and (!($_.StartsWith(";")))`
                                -and (!($_.StartsWith('`')))`
                                -and (($_.Contains('=')))){
                                    $buildAgentProps.add($_.split('=',2)[0],$_.split('=',2)[1])
                                }
                    }

Write-Verbose "Build Agent original settings"
$buildAgentProps.GetEnumerator() | % { "$($_.Name)=$($_.Value)" } | Write-Verbose

$buildAgentProps['serverUrl'] = $serverUrl
$buildAgentProps['name'] = $agentName
$buildAgentProps['ownPort'] = $ownPort
# Write out the keys seen
Write-Verbose "Build Agent updated settings"
$buildAgentProps.GetEnumerator() | % { "$($_.Name)=$($_.Value)" } | Write-Verbose
$buildAgentProps.GetEnumerator() | % { "$($_.Name)=$($_.Value)" } | Out-File $agentDir\conf\buildAgent.properties
}

# Configure service wrapper to allow multiple instances on a single machine
# This rewrites the wrapper config file without comments, if you need the comments, don't supply the agentName when installing to get the default config
if (-Not ($defaultName -eq $true)) {
    $wrapperProps = [ordered]@{}
    $wrapperConf = get-content $agentDir\launcher\conf\wrapper.conf 
    $wrapperConf | %{if (`
                            (!($_.StartsWith('#')))`
                                -and (!($_.StartsWith(';')))`
                                -and (!($_.StartsWith(";")))`
                                -and (!($_.StartsWith('`')))`
                                -and (($_.Contains('=')))){
                                    $wrapperProps.add($_.split('=',2)[0],$_.split('=',2)[1])
                            }
                    }
    Write-Verbose "Java Service Wrapper original settings"
    $wrapperProps.GetEnumerator() | % { "$($_.Name)=$($_.Value)" } | Write-Verbose
    # Name of the service
    $wrapperProps['wrapper.ntservice.name'] = "$agentName"
    # Display name of the service
    $wrapperProps['wrapper.ntservice.displayname'] = "$agentName TeamCity Build Agent"
    # Description of the service
    $wrapperProps['wrapper.ntservice.description'] = "$agentName TeamCity Build Agent Service"
    #$wrapperProps['']
    # Write out the keys seen, can't do it inline because JavaServiceWrapper is picky about encoding
    Write-Verbose "Java Service Wrapper updated settings"
    $wrapperProps.GetEnumerator() | % { "$($_.Name)=$($_.Value)" } | Write-Verbose
    $wrapperProps.GetEnumerator() | % { "$($_.Name)=$($_.Value)" } | Out-File $agentDir\launcher\conf\wrapper.conf -Encoding 'ASCII'
}

# Future state, catch failure and call chocolateyUninstall.ps1 or some other cleanup
# trap exit 1 { Start-ChocolateyProcessAsAdmin "/C `"$agentdir\bin\service.stop.bat; $agentDir\bin\service.uninstall.bat; rm -r -fo $agentDir `"" cmd }
Start-ChocolateyProcessAsAdmin "/C `"$agentDrive && cd /d $agentDir\bin && $agentDir\bin\service.install.bat && $agentDir\bin\service.start.bat`"" cmd

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
TeamCity Build Agent 4.0.1 18 Thursday, November 28, 2019 Approved
TeamCity Build Agent 4.0.0 28389 Wednesday, June 12, 2019 Approved
TeamCity Build Agent 3.0.1 6252 Tuesday, January 22, 2019 Approved
TeamCity Build Agent 3.0.0 8582 Thursday, January 17, 2019 Approved
TeamCity Build Agent 3.0.0-beta-2 69 Thursday, January 17, 2019 Approved
TeamCity Build Agent 3.0.0-beta-1 62 Thursday, January 17, 2019 Approved
TeamCity Build Agent 2.3.0-beta-1 194 Wednesday, July 11, 2018 Approved
TeamCity Build Agent 2.2.1 203565 Friday, April 13, 2018 Approved
TeamCity Build Agent 2.1.2 19657 Thursday, October 19, 2017 Approved
Discussion for the TeamCity Build Agent Package

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.
comments powered by Disqus