Using Check-In and Check-Out › Check-In Process › Check In Files

Check In Files

The check-in process lets you copy files from the client directory system to CA Harvest SCM, creating items and item paths or updating existing items that have changed.

Follow these steps:

1. Navigate the Workbench to the state in which you want to check in files.
2. Right-click the state, and select check-in process from the shortcut menu.

   The check-in process dialog appears.

   Note: The lowercase italic text indicates the process dialog name by the process type, since the process execution dialog names differ to each site.

3. Select a mode:

   Update and Release

   Checks in the file to the repository and the reserved tag is removed from the corresponding item. The permission on the client file is automatically set to read-only so that changes cannot be made to it until it is checked out again.

   Update and Keep

   Updates the item in the view, the current package keeps it reserved and the file permissions unchanged so that you can make more updates.

   Release Only

   Does not check in or update the item and the item is no longer marked as reserved for the current package. The permission on the client file is automatically set to read-only so that the file cannot be changed until it is checked out again.

   Release Only does not require the local file system file to exist.

   Note: Selecting Release Only mode implies an item filter of Existing Items Only because this operation requires existing reserved items in the repository.

4. Click the button next to the Package field to open the Select a Package dialog.

   The Select a Package dialog appears.

5. Select a package to associate with updates to an item, and click OK.

   Your package selection appears in the Package field.

6. Establish a point at which paths in the repository mirror working directories on the client:

   From

   Specifies the client file directory. You can click the button next to this field to open the Browse For Folder dialog that lets you browse through available paths, and select a location.

   Machine

   Displays the remote computer name if the client path is on a remote computer.

   To

   Specifies the path location in the destination view to check in files. To change the path, click the button next to this field to open the Repository Path Selection dialog that lets you browse through available paths, and select a location.

   Note: If the files being checked in include a directory specification, as is the case during recursive check-in, this directory specification is appended to the view path specified here when you specify a preserve structure check-in option.

   The internal (repository) and external (file system) structures are synchronized.

7. Specify the way to check in files to view paths:

   Preserve Directory Structure

   Checks in the selected files to repository view paths with names that correspond to their client directory location if these view paths currently exist.

   Preserve and Create Path Structure

   Checks in selected files to paths with names that correspond to their client directory location and creates any view paths that do not currently exist.

   All Files to Same View Path

   Checks in all selected files to the same path in the destination view and ignores the client directory structure.

   The way you check in the files to view paths is set.

8. Specify how to filter the files being checked in:

   New or Existing Items

   Checks in files if they are reserved by the package or did not previously exist in the repository. A corresponding item does not need to exist in the current view; however, if it is in the current view, it must have a reserved version in the current package.

   New Items Only

   Limits the check-in to files that do not have corresponding items in the current view. If the item has been removed from the current view, you can check in the file using this filter.

   Note: If the corresponding item was renamed in the current project, you cannot check in the file. You must rename the file before you can check it in.

   Existing Items Only

   Limits the check-in to files that have corresponding items reserved by the package. Any files without corresponding items are skipped. This filter helps prevent the existence of unwanted files, such as temporary files or templates, in your repository.

   The check-in filter is set.

9. Select a Placement option:

   Trunk

   Creates versions on the trunk.

   Branch

   Creates versions on a branch.

   The location of the checked-in versions is set.

10. Specify files to check in.

    Note: If you select files in the client directory before invoking the process dialog, the files populate the Files field. You can also select files by clicking Add (the plus [+] sign) to open and use the Find File dialog.

11. Select options, and enter and view information about the check-in:

    Delete files after check in

    Deletes from the client file system all files successfully checked in with the mode Update and Release, or Release Only. Deleted files are also removed from the signature file (harvest.sig) on the client.

12. (Optional) Click the tabs to enter and view information:

    Comment

    Specifies comments.

    Note

    Provides notes about the process.

    Note: If the Enforce Change Description option is selected in the check-in Properties dialog, you cannot execute a check-in successfully without entering a description.

    Click OK.

    The files are checked in.