FIX: Builds in a gated check-in build definition incorrectly run concurrently and job fails in TFS 2010

Issue 1

Consider the following scenario:

• You configure two or more build agents to allow for concurrent build requests in a build controller.

• You select gated check-in as the trigger type when you define a build definition.

• The build definition has two or more build requests in the Queued state while another build request has the InProgress state.

In this scenario, some builds in the build definition might incorrectly run concurrently in the build definition after the build in the InProgress state finishes.

Issue 2

When you try to run build requests in the build controller, the following exceptions are encountered, and the job fails:

Cause of Issue 1

This issue occurs because of an error in the logic that decides which build is the next build.

When the InProgress build is finished, the incorrect logic might start more than one gated submission on a definition.

Cause of Issue 2

This issue occurs because errors exist in the build warehouse adapter and in the test management adapter.

Hotfix information

A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that this article describes. Apply it only to systems that are experiencing this specific problem.

To resolve this problem, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft website:

http://support.microsoft.com/contactus/?ws=supportNote In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.