Resolving a frozen package scenario when the promotion of the package failed?
Article ID: 55443
Updated On:
Products
Issue/Introduction
Consider this scenerio:
- PackageA contains version1 of itemA
- PackageB contains version2 of itemA
- User approves packageB
- User then tries to promote packageB, but the promotion fails because Package A has not yet been promoted, resulting in a package dependency problem.
Environment
Harvest Software Change Manager all versions
Cause
In this situation we have conflicting rules in Harvest.
- Because of "Package Dependency" rules, for the same item, the lower mapped versions must be promoted to the next state before or along with the higher mapped version.
- When a package is approved it is put in a "frozen" state and cannot be changed until promoted to the next state.
- PackageA cannot be promoted because it has not yet been approved.
Since the approval process marks packageB in a frozen state, it is not possible to checkout or delete version2. Neither is it possible to delete version1 because it is the parent version of version2.
Resolution
To resolve the situation, there are a few options:
One would be to go ahead and approve PackageA so that it can be promoted first, or at the same time as PackageB
Another would be to uncheck the "Verify Package Dependency" checkbox when promoting PackageB
A third would be to unfreeze PackageB (reject it), use the Switch Package process to move both versions to the same package, approve that package and promote it. These would be the steps to accomplish this:
- Use the 'reject' process to unfreeze PackageB
- Use the 'switch package' process to move version1 to PacakgeB, or version2 to PackageA
- Promote the package which contains both version1 and version2 to the next state/view
- Delete the remaining package if necessary.
Additional Information
This article in the online documentation provides more information about the complexities when moving packages through your project's lifecycle: Manage Packages in the Life Cycle
Feedback
