Page History

...

• be able to open outbound HTTP connections to the server address (the same address you use in the browser to view the TeamCity UI, configured in buildAgent.properties file)
• have full permissions (read/write/delete) to the following directories recursively: <agent home> (necessary for automatic agent upgrade and agent tools support), <agent work>, <agent temp>, and agent system directory (set by workDir, tempDir and systemDir parameters in buildAgent.properties file)
• be able to launch processes (to run builds).
• be able to launch nested processes with the following parent process exit (this is used during agent upgrade)

Windows

• Log on as a service (to run as Windows service)
• Start/Stop service (to run as Windows service, necessary for the agent upgrade to work, see also Microsoft KB article)
• Debug programs (required for take process dump functionality)

• Reboot the machine (required for agent reboot functionality) 

• To be able to monitor performance of a build agent run as a Windows service, the user starting the agent must be a member of the Performance Monitor Users group

...

• the user must be able to run the shutdown command (for the agent machine reboot functionality and the machine shutdown functionality when running in a cloud environment)
• when using systemd, it shoul dnot kill the processes on the main proces exit (use RemainAfterExit=yes)

Build-related Permissions

...

To run agent automatically on the machine boot under Linux, configure daemon process with the agent.sh start command to start it and agent.sh stop command to stop it. Refer to an example procedure below

For systemd, check example confiuration file:

For init.d refer to an example procedure:

1. Navigate to the services start/stop services scripts directory:

...