Can older versions be deleted?
search cancel

Can older versions be deleted?

book

Article ID: 10316

calendar_today

Updated On:

Products

CA Harvest Software Change Manager - OpenMake Meister CA Harvest Software Change Manager CA Harvest Software Change Manager - OpenMake Meister

Issue/Introduction

We would like to delete some older versions and packages, but leave newer versions in the project. But when we try to delete we get following message:

---------- Begin <Delete Version> Process --------------- 
I00060052: Delete Versions Owner Only execution was successful.
E0302001e: Cannot delete version <#> of <file name>; a later version exists.
E03060019: Process Execute failed. Process Name: Delete Version - Owner Only.
---------- End <Delete Version> Process ---------------

The reason we would like to delete these older versions is that there are few packages sitting in the dev state from last year. Project team wants to do cleanup. Most probably someone was working and left the company, other developer did not realize and moved on to this change to production and might be there are already several versions in the production. So basically I would like to know how to cleanup this issue.



Environment

Harvest Software Change Manager all versions

Resolution

Harvest is designed to maintain the complete history of every file checked in from version 0 through to the current version, so deleting some intermediate versions is not possible with Harvest as it would lead to an incomplete history of the file.

While Harvest does not allow you to delete older versions while leaving newer versions in place, what you can do is demote those versions to a state that does not have a view assigned, and this will make them invisible to the other states.

Using the Administrator Tool, in your project create a state named "Archive" and in the "View" field select "No View".  Leave the "All snapshot" checkbox unchecked.

Next, make sure that all your states have a "Demote" process that demotes back to the previous state.  In your initial state, create a "Demote" process to demote to the "Archive" state.  For all your demote processes make sure the "Enforce Package Bind" and "Verify Package Dependency" checkboxes are unchecked.

With these settings in place, you can now demote any packages back through all the states and then demote it into the "Archive" state.  Those packages and versions will no longer be visible from the other views.

Additional Information

If you later decide you want to make those packages and versions visible again, simply promote them from the TrashBin state to your initial state.

For more information, see these chapters in the online documentation:

Understanding Versions

Manage Versions, Items, and Paths

Define Lifecycle Processes - Define a Demote Process

Administrate Projects and Lifecycles - Create a State