Downloads:

50,436

Downloads of v 2018.2.3:

375

Last Update:

10 Mar 2019

Package Maintainer(s):

Software Author(s):

  • JetBrains

Tags:

Testing Build Coding Compilation Continuous Integration CI jetbrains admin

TeamCity Continuous Integration Server

This is not the latest version of TeamCity Continuous Integration Server available.

  • 1
  • 2
  • 3

2018.2.3 | Updated: 10 Mar 2019

Downloads:

50,436

Downloads of v 2018.2.3:

375

Maintainer(s):

Software Author(s):

  • JetBrains

  • 1
  • 2
  • 3
TeamCity Continuous Integration Server 2018.2.3

This is not the latest version of TeamCity Continuous Integration Server available.

  • 1
  • 2
  • 3

Some Checks Are Exempted or Have Failed

Not All Tests Have Passed


Validation Testing Passed


Verification Testing Failed

Details

Scan Testing Exemption for this package version only:

Details
Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install TeamCity Continuous Integration Server, run the following command from the command line or from PowerShell:

>

To upgrade TeamCity Continuous Integration Server, run the following command from the command line or from PowerShell:

>

To uninstall TeamCity Continuous Integration Server, run the following command from the command line or from PowerShell:

>

Deployment Method:

📝 NOTE: 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

  • 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. Copy Your Script

choco upgrade teamcity -y --source="'INTERNAL REPO URL'" --version="'2018.2.3'" [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 teamcity -y --source="'INTERNAL REPO URL'" --version="'2018.2.3'" 
$exitCode = $LASTEXITCODE

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

Exit $exitCode

- name: Install teamcity
  win_chocolatey:
    name: teamcity
    version: '2018.2.3'
    source: INTERNAL REPO URL
    state: present

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


chocolatey_package 'teamcity' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '2018.2.3'
end

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


cChocoPackageInstaller teamcity
{
    Name     = "teamcity"
    Version  = "2018.2.3"
    Source   = "INTERNAL REPO URL"
}

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


package { 'teamcity':
  ensure   => '2018.2.3',
  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.

Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...

This package was approved as a trusted package on 11 Mar 2019.

Description

Powerful Continuous Integration out of the box.

Professional edition of TeamCity is free forever and provides access to all product features, support via the forum and issue tracker, 100 build configurations, and 3 build agents. It is a perfect fit for small teams and individual developers.

Package Specific

Package Parameters

The following package parameters can be set:

  • /unzipLocation: - Root directory to install TeamCity service (defaults to c:\, which results in c:\TeamCity being used. A TeamCity folder is always created, so the actual install path is C:\TeamCity for the default case or path\TeamCity with a custom option)
  • /RunAsSystem - Run as SYSTEM user (defaults to true. If false, then username/password must be set)
  • /ServiceName: - Name of TeamCity Windows service (defaults to 'TeamCity')
  • /Domain: - Windows service domain
  • /Username: - Windows service username
  • /Password: - Windows service password

To pass parameters, use --params "''" (e.g. choco install packageID [other options] --params="'/ITEM:value /ITEM2:value2 /FLAG_BOOLEAN'").
To have choco remember parameters on upgrade, be sure to set choco feature enable -n=useRememberedArgumentsForUpgrades.

Example:
choco install teamcity --params "'/username=*user* /password=*password*'"


tools\chocolateyHelpers.ps1
function Get-ChocolateyPackageTempFolder {
    param(
      [string] $packageName
    )
    $chocTempDir = Join-Path $env:TEMP 'chocolatey'
    $tempDir = Join-Path $chocTempDir "$packageName"
    if (![System.IO.Directory]::Exists($tempDir)) {[System.IO.Directory]::CreateDirectory($tempDir) | Out-Null}
   
    return $tempDir
}

function Set-ChocolateyPackageOptions {
    param(
        [Parameter(Mandatory=$True,Position=1)]
        [hashtable] $options
    )
    $packageParameters = $env:chocolateyPackageParameters;

    if ($packageParameters) {
        $parameters = ConvertFrom-StringData -StringData $env:chocolateyPackageParameters.Replace(" ", "`n")
        $parameters.GetEnumerator() | ForEach-Object {
           $options[($_.Key)] = ($_.Value)
        }
    }
}
tools\chocolateyInstall.ps1
$checksum = 'af82cf71c03ba7eee9e0488f294b6cc06acd7b7a2ef22907f3a470c3a1420877'

$options = @{
  version = $env:ChocolateyPackageVersion;
  unzipLocation = 'C:\';
  runAsSystem = $true;
  serviceName = 'TeamCity';
  userName = '';
  domain = '';
  password = '';
}

# https://download.jetbrains.com/teamcity/TeamCity-2018.1.4.tar.gz.sha256 
$packageParameters = @{
  packageName = 'teamcity';
  url = "https://download.jetbrains.com/teamcity/TeamCity-$($options['version']).tar.gz";
  checksum = $checksum;
  checksumType = 'Sha256';
}

if(!$PSScriptRoot){ $PSScriptRoot = Split-Path $MyInvocation.MyCommand.Path -Parent }
. "$PSScriptRoot\ChocolateyHelpers.ps1"

Set-ChocolateyPackageOptions $options
if ($options['userName'] -ne '' -and $options['password'] -ne '') {
  $options['runAsSystem'] = $false;
}

$service = Get-Service | Where-Object Name -eq $options['serviceName']
if ($service -ne $null) {
  Stop-Service $service
}

$binPath = Join-Path $options['unzipLocation'] 'TeamCity\bin'
if ((Test-Path $binPath) -and ($service -ne $null)) {

  Push-Location $binPath
  Start-ChocolateyProcessAsAdmin '.\teamcity-server.bat service delete'
  Pop-Location
}

$tempFolder = Get-ChocolateyPackageTempFolder $packageParameters['packageName']
$downloadFile = Join-Path $tempFolder "TeamCity-$($options['version']).tar.gz"
$tarFile = Join-Path $tempFolder "TeamCity-$($options['version']).tar"
Get-ChocolateyWebFile @packageParameters -FileFullPath $downloadFile
Get-ChocolateyUnzip -FileFullPath $downloadFile -Destination $tempFolder
Get-ChocolateyUnzip -FileFullPath $tarFile -Destination $options['unzipLocation']

Push-Location $binPath
$args = New-Object System.Collections.ArrayList

$args.Add('service') | Out-Null
$args.Add('install') | Out-Null

if ($options['runAsSystem']) {
  $args.Add('/runAsSystem') | Out-Null
}
else {
  $args.Add("/user=`"$($options['userName'])`"") | Out-Null
  $args.Add("/password=`"$($options['password'])`"") | Out-Null
  if ($options['domain'] -ne '')
  {
    $args.Add("/domain=`"$($options['domain'])`"") | Out-Null
  }
}
$joined = $($args -join ' ')
Start-ChocolateyProcessAsAdmin ".\teamcity-server.bat $joined"
Pop-Location

$options['password'] = '';
Export-CliXml -Path (Join-Path $PSScriptRoot 'options.xml') -InputObject $options

Remove-Item $tarFile
tools\chocolateyUninstall.ps1
$optionsFile = (Join-Path $PSScriptRoot 'options.xml')

if (!(Test-Path $optionsFile)) {
  throw 'Install options file missing. Could not uninstall.'
}

$options = Import-CliXml -Path $optionsFile

$service = Get-Service | Where-Object Name -eq $options['serviceName']
if ($service -ne $null) {
  Stop-Service $service
}

$binPath = Join-Path $options['unzipLocation'] 'TeamCity\bin'
if ((Test-Path $binPath) -and ($service -ne $null)) {
  Push-Location $binPath
  Start-ChocolateyProcessAsAdmin '.\teamcity-server.bat service delete'
  Pop-Location
}


Remove-Item (Join-Path $options['unzipLocation'] 'TeamCity') -Recurse -Force

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.

Add to Builder Version Downloads Last Updated Status
TeamCity Continuous Integration Server 2022.04.1 66 Thursday, June 2, 2022 Exempted
TeamCity Continuous Integration Server 2022.04 47 Friday, April 29, 2022 Exempted
TeamCity Continuous Integration Server 2021.2.3 58 Friday, February 18, 2022 Exempted
TeamCity Continuous Integration Server 2021.2.2 146 Tuesday, January 11, 2022 Exempted
TeamCity Continuous Integration Server 2021.2.1 71 Tuesday, November 30, 2021 Exempted
TeamCity Continuous Integration Server 2021.2 72 Tuesday, October 26, 2021 Exempted
TeamCity Continuous Integration Server 2021.1.4 59 Saturday, October 9, 2021 Exempted
TeamCity Continuous Integration Server 2021.1.3 72 Thursday, September 9, 2021 Exempted
TeamCity Continuous Integration Server 2021.1.2 81 Tuesday, August 3, 2021 Exempted

Discussion for the TeamCity Continuous Integration Server Package

Ground Rules:

  • This discussion is only about TeamCity Continuous Integration Server and the TeamCity Continuous Integration Server 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 Continuous Integration Server, 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