Forge Home


Installs TeamCity agents


11,324 latest version

2.8 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

  • 0.0.4 (latest)
  • 0.0.3
  • 0.0.2
  • 0.0.1
released Oct 15th 2016

Start using this module

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

Add this module to your Puppetfile:

mod 'wknapik-teamcity_agent', '0.0.4'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add wknapik-teamcity_agent
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install wknapik-teamcity_agent --version 0.0.4

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.



wknapik/teamcity_agent — version 0.0.4 Oct 15th 2016


Scenario 1: set up 8 agents, with default settings (recommended).

Agent names will be $fqdn-01 .. $fqdn-08, they will listen on ports 9090 ..

9097, will be installed in /home/teamcity/agent/ and a cron entry will be

added for each to run every 5min and call start.

$range = range(1, 8) teamcity_agent::agent { $range : server_url => '' }

Scenario 2: set the agent name and port explicitly.

teamcity_agent::agent { 'foo': server_url => '' own_port => 6666, }

Scenario 3: set all options explicitly.

teamcity_agent::agent { 'my bar': user => 'ci', server_url => '',

# If you want $name != $agent_name.
agent_name => 'bar', 
own_address => '',
own_port => 9999,
properties => 'some.prop = qux',
with_cron => false



Based on