Check In Pending Changes that Are Controlled by a Gated Check-in Build
If you are checking in files to a version control folder that is controlled by a gated check-in build, there are some additional steps that you must take to complete the check-in operation.
Required Permissions
To perform these procedures, you must have the Check in and the View builds permission set to Allow. For more information, see Team Foundation Server Permissions.
Begin Checking in Changes to a Folder that is Controlled by a Gated Check-in Build
If the Gated Check-in dialog box appears during the check-in process (as described in Check In Pending Changes) then your changes must first be built by Team Foundation Build before they can be checked in.
To check in changes to a folder that is controlled by a gated check-in build
In the Gated Check-in dialog box, find the Build definition menu and perform one of the following steps:
If a build definition is displayed, proceed to the next step.
If the Build definition menu is displayed instead of the name of a build definition, then notify your build administrator that there are two or more build definitions that control the same version control folder. On the Build definition menu, select the build definition that your build administrator suggests that you use.
Perform one of the following steps:
Cancel the check-in operation and continue working: If you do not want to try building your changes yet, click Cancel, and then when the system asks you if you want to delete the shelveset, click Yes.
Cancel the check-in operation and start a private build of your changes: If you want to build the code yourself in a private build, click Cancel. When the system asks if you want to delete the shelveset, make a note of the name of the new shelveset, and then click No. You can now build the shelveset manually. For more information, see Queue a Build.
Proceed with the check-in operation, while keeping your changes in your workspace: To proceed with the check-in operation and continue working with your changes, see Proceed with the Gated Check-in after Keeping the Changes in Your Workspace.
Proceed with the check-in operation, while deleting changes in your workspace: If you do not need to continue working with your changes, see Proceed with the Gated Check-in after Deleting the Changes in Your Workspace.
Bypass the gated check-in requirement: If you have the Override check-in validation by build permission set to Allow, you can bypass the gated check-in requirement. Click Show options, and then select Bypass validation build and check in my changes directly (requires permissions).
Proceed with the Gated Check-in after Keeping the Changes in Your Workspace
The gated check-in process provides a way to proceed with the check-in and continue working with your changes. The drawback of proceeding in this way is that if the build completes successfully you must reconcile the changes in your workspace with the changes that are checked into version control.
To proceed with the gated check-in after keeping your changes in your workspace
Follow the steps in Begin Checking in Changes to a Folder that is Subject to Gated Check-in.
The Gated Check-in dialog box appears.
Click Build Changes.
The Queued tab of the Build Explorer appears. The name of your gated check-in build is shown next to the Check-in Shelveset
.gif "Check-in Shelveset")
icon.Monitor the build by using Build Explorer, the Build Notifications application, or build notification e-mail. For more information, see Monitor Progress of a Running Build.
After the build is complete, perform one of the following steps:
If the build succeeded, then your changes are checked in. It is recommended that you reconcile your workspace before you continue to work on the codebase:
Go to the Completed tab of Build Explorer. For more information, see Use Build Explorer to View and Manage Queued, Ongoing, and Completed Builds.
Find the successfully completed gated check-in build, which is shown next to a Check-in Shelveset
icon.Right-click the build and then click Reconcile Workspace.
If the build failed, then your changes are not checked in. To correct the problems that caused the build to fail, perform the following steps:
Use Build Explorer to open the completed build. For more information, see Use Build Explorer to View and Manage Queued, Ongoing, and Completed Builds.
In the completed build window, read the information that can help you resolve the problem that caused the build to fail. For some types of problems, you may be able to click the error or issue to view the file that requires corrections.
In your files, correct the problems that caused the build to fail.
Proceed with the Gated Check-in after Deleting the Changes in Your Workspace
If you want to proceed with the gated check-in operation and you do not plan to continue working with your changes, you can delete the changes in your workspace. Your changes are preserved in a shelveset and built by the system. If the build completes, then your changes are checked in. If the build fails, then you can unshelve the shelveset to get the changes back into your workspace.
To proceed with the gated check-in after deleting changes in your workspace
Follow the steps in Begin Checking in Changes to a Folder that is Subject to Gated Check-in.
The Gated Check-in dialog box appears.
In the Gated Check-in dialog box, click Show Options and then clear Preserve my pending changes locally.
Click Build Changes.
The Queued tab of the Build Explorer appears. The name of your gated check-in build is shown next to the Check-in Shelveset
icon.Monitor the build by using Build Explorer, the Build Notifications application, or build notification e-mail. For more information, see Monitor Progress of a Running Build.
After the build is complete, perform one of the following steps:
If the build succeeded, then your changes are checked in.
(Optional) Get the latest version of the files so that your workspace contains the changes that you checked in. For more information, see Update File Versions in Your Workspace.
If the build failed, then your changes are not checked in. To correct the problems that caused the build to fail, perform the following steps:
Use Build Explorer to open the completed build. For more information, see Use Build Explorer to View and Manage Queued, Ongoing, and Completed Builds.
In the completed build window, read the information that can help you resolve the problem that caused the build to fail. For some types of problems, you may be able to click the error or issue to view the file that requires corrections.
Retrieve your changes from the shelveset. For more information, see Shelve and Unshelve Pending Changes.
In your files, correct the problems that caused the build to fail.