Forge Home


Module to manage teamcity installations


7,967 latest version

4.2 quality score

We run a couple of automated
scans to help you access a
module's quality. Each module is
given a score based on how well
the author has formatted their
code and documentation and
modules are also checked for
malware using VirusTotal.

Please note, the information below
is for guidance only and neither of
these methods should be considered
an endorsement by Puppet.

Version information

  • 2.0.0 (latest)
  • 1.0.5
  • 1.0.4
  • 1.0.3
  • 1.0.2
  • 1.0.1
released Feb 11th 2016
This version is compatible with:
  • , ,

Start using this module

  • r10k or Code Manager
  • Bolt
  • Manual installation
  • Direct download

Add this module to your Puppetfile:

mod 'neillturner-teamcity', '2.0.0'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add neillturner-teamcity
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install neillturner-teamcity --version 2.0.0

Direct download is not typically how you would use a Puppet module to manage your infrastructure, but you may want to download the module in order to inspect the code.



neillturner/teamcity — version 2.0.0 Feb 11th 2016

Puppet TeamCity module

The TeamCity puppet module downloads and installs the latest version of TeamCity. Also allows plugins to be installed.

Tested on CentOS 6.x.

Minimal TeamCity::Server - Usage:

 class { 'oraclejava::jdk7_rpm': }
 class { 'teamcity::server':
    require => Class['oraclejava::jdk7_rpm'],

 teamcity::server::plugin { 'node':
    plugin_url       => '',
    plugin_zip_file  => '',
    require          => Class['teamcity::server'],

This stanza does not include a default build agent; see below. Memory options are configured to be the production values, so you'll need around 750 MiB for the server's runtime.

TeamCity::Agent - Usage:

When installing the agent, you first need a TeamCity server up and running, I run mine at the A-name 'tc'. This is in the defaults of teamcity::agent, so if you have a different name for your TeamCity server, I suggest you override it in hiera:


Besides, that, here's a sample configuration profile that uses the TeamCity Agent class:

 class { 'oraclejava::jdk7_rpm': }
 class { 'teamcity::agent':
    require => Class['oraclejava::jdk7_rpm'],

Complex TeamCity::Server - Usage:

Install via an http proxy and configure port, directories etc

 class { 'oraclejava::jdk7_rpm':
      download_url  => '',
      wget_opts   => "-e use_proxy=yes -e http_proxy=  -e https_proxy=",

 class { 'teamcity::server':
    team_city_version => '8.1.4',
    data_dir          => '/data/teamcity-server',
    plugin_dir        => '/data/teamcity-server/plugins'
    db_type           => 'mysql',
    port              => '8000', 
    address           => '',
    wget_opts         => "-e use_proxy=yes -e http_proxy=",
    http_proxy_host   => '',
    http_proxy_port   => '3128',
    https_proxy_host  => '',
    https_proxy_port  => '3128',
    require           => Class['oraclejava::jdk7_rpm'],
 teamcity::server::plugin { 'node':
    plugin_url       => '',
    plugin_zip_file  => '',
    wget_opts        => "-e use_proxy=yes -e http_proxy= -e https_proxy=",
    require          => Class['teamcity::server'],

It's worth noting that if you change the folders in the agent-class to be outside of their default you're going to have to hack Catalina and a range of other software you haven't touched before, to make it work. Simply, I couldn't, despite spending about 3 hours on it, so just go with the default folders.

You'll need about 400 MiB minimum for each agent you want to run on a node.



Good reading