Unable to render embedded object: File (TeamCity48.png) not found.

TeamCity 10.x and 2017.x Documentation

Icon

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

Key

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

...

    1. The TeamCity server detects a change in your VCS Root and stores it in the database.
    2. The build trigger sees the change in the database and adds a build to the queue.
    3. The server finds an idle compatible build agent and assigns the queued build to this agent.
    4. The agent executes the Build Steps. While the build steps are being executed, the build agent reports the build progress to the TeamCity server sending all the log messages, test reports, code coverage results, etc. to the server on the fly, so you can monitor the build process in real time.
    5. After finishing the build, the build agent sends Build Artifacts to the server. 

Now you can proceed with TeamCity installation.