Skip to end of metadata
Go to start of metadata
You are viewing documentation of TeamCity 6.5.x, which is not the most recent released version of TeamCity. Please refer to the listing to choose another version.
Search

Table of Contents

In TeamCity a build agent contains two processes:

  • Agent Launcher — Java process that launch the agent process itself
  • Agent — main process for a Build Agent; runs as a child process for the agent launcher

Whether you run a build agent via the agent.bat|sh script or as a Windows service, at first the agent launcher starts and then it starts the agent.
For both processes you can customize the final agent behavior by specifying system properties and variables to run with.

Icon

You do not need to specify any of the options unless you are advised to do by TeamCity support team or you know what you are doing.

In this section:

Agent Launcher Properties

Build Agent Is Run Via Script

Before you run the <Agent Home>\bin\agent.bat|sh script, set the TEAMCITY_LAUNCHER_OPTS environment variable.

Build Agent Is Run As Service

In the <Agent Home>\launcher\conf\wrapper.conf file, add the following lines (one per option, the N number should increase):

Icon

Please ensure to re-number all the lines after the inserted ones.

Agent Properties

Build Agent Is Run Via Script

Before you run the <Agent Home>\bin\agent.bat|sh script, set the following environment variables:

  • TEAMCITY_AGENT_MEM_OPTS — Set agent memory options (JVM options)
  • TEAMCITY_AGENT_OPTS — additional agent JVM options

Build Agent Is Run As Service

In the <Agent Home>\launcher\conf\wrapper.conf file, add the following lines (one per option):

Icon
  • You should add additional lines before the following line in the wrapper.conf file:
  • Please ensure to re-number all the lines after the inserted ones.



See also: