You are viewing the documentation of TeamCity 10.x and 2017.x, which is not the most recently released version of TeamCity.
View this page in the latest documentation or refer to the listing to choose the documentation corresponding to your TeamCity version.


Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


  • run the build in TeamCity and see it misbehaving
  • disable the agent so that no other builds run on it. This can be done while the build is still in progress
  • log in to the agent machine using the same user as the one running the TeamCity agent (check the right user in the machine processes list)
  • stop the agent
  • in a command line console, "cd" to the checkout directory of the build in question (the directory can be looked up in the beginning of the build log in TeamCity)
  • run the build with a command line as you would do on a developer machine. This is runner-dependent. (For some runners you can look up the command line used by TeamCity in the build log, see also the logs\teamcity-agent.log agent log file for the command line used by TeamCity)
  • if the build fails - investigate the reason as the issue is probably not TeamCity-related and should be investigated on the machine.
  • if it runs OK, continue
  • in the same console window "cd" to <TeamCity agent home>\bin and start TeamCity agent from there with the agent start command
  • ensure the runner settings in TeamCity are appropriate and should generate the same command line as you used manually. e.g. use "Command Line" build step with "Custom script" option and the same command which can be saved in a .sh or .bat file and run from the command prompt
  • run the build in TeamCity selecting the agent in the Run custom build dialog
  • when finished, enable the agent