Before starting this section of the tutorial, select a Visual Studio project in TFS that meets the following criteria:
- You can make changes to and commit.
- Has a TFS build definition that will automatically get triggered upon commit.
- You are able to define project alerts on TFS events, or that you can get an administrator to help you with.
- Produces an output artifact such as compiled code in the form of an .exe, .zip, .msi, etc.
Configure TFS Checkin Push
In TFS, go to the administration page for the project,
New. Scope is your choice, Alert Category is
Checkin - Any checkin occurs in this team project. Click OK.
On next screen, name the alert appropriately. Choose appropriate Alert Filters as needed. Suggested is only have Field =
Team Project, Operator as =, and Value = the project name.
Change the Format to
SOAP. The Send To will be a URL as follows:
- continuumaddress will be the address of the VersionOne Continuum server
- continuumproject will be the project created in the first step of this tutorial
- apitoken will be the user’s api token found above
Save and Close
Submit a Change
In Visual Studio, make a change and commit it so that Visual Studio pushes the change to TFS. Within a few seconds, TFS will push a SOAP message to the VersionOne Continuum REST api endpoint which will then get parsed and associated with the VersionOne Continuum project.
To see if the change made it to VersionOne Continuum and got associated with the project click
projects on the top menu and then select your project. Select the Manifest tab. You changes should be there.
The changes will queue up until the build complete message comes in to kick off the job.
Click here to continue on with the tutorial once the Stash changes are viewable in VersionOne Continuum.