Selecting versions to export by filtering

Edit online

If you have VOBs with files that have long version histories, you can specify filtering during the export command to import only a subset of versions.

Versions that get exported are called "selected versions," whereas the versions that do not get exported are “filtered." Regardless of the filtering, the versions are always selected back to /main/0.

You can filter versions with the following options of the ccc export ccase command:
  • ccc export ccase --noHistory: Versions selected by view.
  • ccc export ccase --noMergePredecessors: Versions selected by views and their predecessors.
  • ccc export ccase --onlyPredecessors: Versions selected by views, predecessors, and merge sources. (This is called a "merge closure.")
  • ccc export ccase --noObsoleteBranches: Versions selected that are on non-obsolete branches or branch types.
  • ccc export ccase --since <date>: Versions selected that are created since a specific time.
Important: If you do not specify a filtering option, all of the versions on all of the branches are exported by default.
When a version is filtered, and it is the end point for a merge, the exporter acts as if the merge is between its successor and the start point for the merge. When a version is filtered, and it is the start point for a merge, the exporter acts as if the merge is between its predecessor and the end point for the merge. When a selected version's predecessor is filtered, its predecessor is recorded as the next selected version between it and /main/0 as you move up the Rational® ClearCase® version tree.
Note: You must be careful when selecting filtering options. Unless you select the "merge closure" option, then you might not be able to incrementally import more versions and have the newly imported versions display in the merge history in Rational Team Concert source control the same way they display in the Rational ClearCase version tree.