Sign up for free

Choose your product:

Set up a build in the cloud

info Build is in preview. Learn more.

Define the build

Create a continuous integration build definition to catch problems early by building your code automatically every time you check it in.

  1. If you haven't already, upload your code to TFS.

  2. In Visual Studio's team explorer, go to the builds page to create a build definition.

    Builds in the VS Team Explorer menu
    New build definition in the VS Team Explorer builds page
  3. Give it a name.

    Name and optional description in the general tab of the build definition dialog
  4. Set the trigger to indicate when to run the build. In this case, we'll use the CI trigger to run the build whenever code is checked in.

    Continuous integration radio button in the trigger tab of the build definition dialog
  5. In Workspace, for the purpose of this exercise, you can map the team project. You must also cloak the Drops folder so that you don't waste time and computer resources.

    Use default folders in the workspace tab of the build definition dialog
  6. In Build Defaults, select Hosted Build Controller. If your team needs the binaries from this build, you should drop them to the server.

    Choose hosted build controller, and copy build output to source control in the build defaults tab of the build definition dialog
  7. In Process, provide the path to what you want to build.

    In our case, it's: Build $/FabrikamFiber/HelloWorld/HelloWorld.sln

    In the process tab, build process parameters, items to build: choose the path in the code repository to the items you want to build

    Save your new build definition. Now, whenever you check in code for this solution, it'll be built automatically.

Queue the build

  1. Right-click the build and queue it to make sure it works.

    Queue new build in the builds page of the Team Explorer
    Queue button on the queue build dialog
  2. Your build is queued.

    The queued build appears under My Builds in the builds page of the Team Explorer

    Done! You've created your first build in the cloud and, because it's a continuous integration build, any time a team member checks in new code, a build is kicked off. And, this can go a long way in helping your team find and fix build-related issues early.

Did you run into problems?

Try this next

Or, dig deeper on MSDN:

Sign up for free