Your Daily Mark.Net

Team Development with Visual Studio Team Foundation Server

The guideline of Team Development with Visual Studio Team Foundation Server is available.

Deleting a team build

I had added a couple of team tests to get our daily build right. But now delete the team builds....

http://msdn2.microsoft.com/en-us/library/ms181719(VS.80).aspx 

Create a team build with team foundation server

Creating a team build is not that of a problem. In VS2005 use the wizard and it is pretty straight forward.

In my case we had some issues. Let me explain the context:

1. to execute the build we use a dedicated build server.
2. After the build we want the unit test to be executed and the code analysis performed.
3. The build is executed by a system account

The first issue was that to perform a build was that the step to add changesets and update workitems was slow....

When you are trying to get the build process right that is a pain in the ass.

So luckily you can skip the  part of adding changesets and updating workitems. the way to do that is check out the TFSBuild.proj and edit it:

1. change <UpdateAssociatedWorkItems>true</UpdateAssociatedWorkItems> to <UpdateAssociatedWorkItems>false</UpdateAssociatedWorkItems>

2. To disable work items and changesets for all builds for a particular build type, add the following to your TFSBuild.proj above the project closing tag:-

   <Target Name="GetChangeSetsAndUpdateWorkItems" > </Target>
   <Target Name="GetChangeSetsOnBuildBreak"  > /Target>
   These two targets are defined in the global TeamBuild.target file. MSBuild allows you to override these targets.

See also this post.
 

So now it's possible to test the build quickly.  

Up to the next problem. When we use the Test view in VS2005 to execute all the unit tests, all tests passed. But in the build process a lot of tests failed. That because some dll's were not copied to the deployment directory. This can be fixed to do the following steps:

1. in VS2005 go to  Test -> Edit test run Configuration  ->  Local test run.
2. go to Deployment and add the missing dll's.
3. click close.

Now the build runs smoothly but now we entered an error publishing the test results. That was caused due to lack of rights at the share of the drop location.

The rights of the build account were set right but the rights of the account that runs the team foundation server had not the proper rights. After adding that specific account  the build runs oke.

Mark