Removing unnecessary baselines

The following steps show you how to mark a baseline for deletion, which removes an unnecessary baseline.

To remove an unnecessary baseline, first mark it for deletion. Set up the Save Offline and Delete command to automatically delete baselines that are marked for deletion when they are no longer used.

(The soad Command enables you or the CM administrator to delete the baselines you have marked.)

Procedure

  1. Find the baselines that you want to remove.

    Find > Baselines

  2. In the Query dialog box, set the query criteria and then run the query.
    1. Set For Release to the appropriate release.
    2. Click the plus sign to add another property to the query.
    3. Set With Purpose to Integration Testing.
    4. Run the query by clicking query icon.
  3. Mark the unnecessary baseline for deletion.

    Choose all baselines that you want deleted, then right-click and select Delete.

    The Delete dialog box displays the selected baselines. Click Delete. The selected baselines are now marked for deletion.

    An update operation does not select a baseline that is marked for deletion. If your team uses project groupings, and any of the project groupings are using marked baselines, they choose different baselines during the update operation.

    The CM administrator sets up the Save Offline and Delete command. The command automatically deletes baselines that are marked for deletion when they are no longer used. For details, see the save_offline_and_delete command.

    Your site might decide to inactivate the release you have finished. Use the Deleting cache files to clean out the process rules and any old releases from the release.

    Retaining the extra releases and process rules does not cause problems. Clean up is for convenience. Cleaning out the releases and the process rules makes it easier to find relevant information in corresponding dialog boxes.

    Additionally, you cannot delete a baseline while a project grouping uses that baseline, or while a process rule uses the baseline. If you try to delete a baseline and its checked-in projects and products, and one or more of its associated projects or products is a member of a project that is not part of the baseline, the delete baseline operation succeed. However, the projects or products are not deleted. Furthermore, if projects in the baseline are members of another baseline, or are baseline projects, the delete operation is successful, but the projects are not deleted.

    Remove obsolete project hierarchies, and then resulting empty project groupings, before you can delete old baselines. However, empty project groupings might still carry important information about tasks the owner explicitly added to or removed from that grouping.

    To find and remove empty project groupings that also have no explicitly added or removed tasks, use the following commands:

    ccm set role ccm_admin

    ccm query –t project_grouping "is_no_project_grouping() and has_no_added_task_in_pg() and has_no_removed_task_in_pg()"

Results

ccm delete @Mark a baseline for deletion


Feedback