On the Code hub for your team project in VSTS/TFS, select the option to Import repository.

In the Import a Git repository dialog box, paste the above URL into the Clone URL text box.

Click Import to copy the sample code into your Git repo.

To fork the sample app into your own GitHub repository:

Navigate to the above GitHub repository URL in your browser.

Select Fork to create your own copy of the repository.

The sample app in this repository is a Java servlet using JavaServer Pages (JSP). Tests for the application are written using JUnit. A Gradle wrapper file is used to build, test, and package the application into a web archive (.war) file.

Set up continuous integration

A continuous integration (CI) process automatically builds and tests code every time a team member commits changes to version control. Here you'll create a CI build definition that helps your team keep the master branch clean.

Observe that the new build definition is automatically linked to your repository.

Select your version control repository. You'll need to authorize access to your repo.

Click the Triggers tab in the build definition. Enable the Continuous integration trigger. This will ensure that the build process is automatically triggered every time a change is committed to your repository.

A new build is started. You'll see a link to the new build on the top of the page. Click the link to watch the new build as it happens.

View the build summary

Once the build completes, select the build number to view a summary of the build.

Notice the various sections in the build summary - the source version of the commit in build details section, list of all associated changes, links to work items associated with commits, and test results.
When the build is automatically triggered by a push to your Git repository, these sections are populated with all the relevant information.

Next steps

You've just put your own CI process in place to automatically build and validate whatever code is checked in by your team. You can also automatically deploy your app. To learn more, see one of these topics: