Choosing automatic or manual check-in

As you update the project artifacts in the Rational Team Concert™ source control, the changes are reflected in the Unresolved folder of the component in the Pending Changes window. You must manually check in the changes to the repository workspace. You can also automate the check-in process whenever you save the file.

About this task

To automate the check-in process, in Microsoft® Visual Studio, click Tools > Options. Expand Source Control and click Jazz Source Control, select the Auto check-in local changes check box and click OK.

If there are large number of files to be checked in and there is an error in a file that is checking in, the check-in process stops and none of the files are checked in. To enable partial check-in if there are errors in files, in Microsoft Visual Studio, click Tools > Options > Source Control > Jazz Source Control, and select the Allow partial check-in (if there are errors) when check-box. You can specify a threshold value in Number of files added/modified exceeds for partial check-in. The threshold value indicates application of partial check-in only after unresolved changes meet or exceed this threshold value.

To manually check in changes:

Procedure

  1. In the Pending Changes window, navigate to the Unresolved folder of the component that contains the unresolved changes. To manually refresh the Pending Changes window, from the toolbar, click the Refresh icon Refresh. To refresh or not the sandbox when you manually refresh the Pending Changes window, in Microsoft Visual Studio, click Tools > Options > Source Control > Jazz Source Control, and select the Refresh sandbox also checkbox.
  2. To check in all changes, right-click Unresolved and click Check-in All. To check in a file, right-click the file and click Check-in > New Change set. The checked-in changes move to the Outgoing folder in the Pending Changes tool window.

What to do next

You can now associate a work item and deliver the changes.

Feedback