Microsoft CI system

Continuous Integration (CI) is a development practice that requires developers to integrate code into a shared repository several times a day. Each check-in is then verified by an automated build, allowing teams to detect problems early.

The following flowchart depicts Microsoft’s CI system.

Figure: Microsoft CI system

In general, the workflow is as follows:

  1. From Visual Studio, a build is triggered after the source code is checked in and sent to Team Foundation Server.
  2. From Team Foundation Server, a build command is sent to Build Server. Inside Build Server, Build Controller compiles the selected project and sends it to Build Agent.
  3. After finishing the build, Build Server sends the new build back to Team Foundation Server.
  4. Team Foundation Server submits the test information to the Microsoft Test Controller.
  5. Test Controller sends the test information to Microsoft Test Agent.
  6. After the execution completes, Test Controller collects the test results from Test Agent.
  7. Test Controller collects and publishes test results to Team Foundation Server.
  8. Team Foundation Server displays the test results to the client.

Copyright © 2021 LogiGear Corporation. All rights reserved. LogiGear is a registered trademark, and Action Based Testing and TestArchitect are trademarks of LogiGear Corporation. All other trademarks contained herein are the property of their respective owners.

LogiGear Corporation

1730 S. Amphlett Blvd. Suite 200, San Mateo, CA 94402

Tel: +1(800) 322-0333