If promoting packages from one state to another one, problems occurred with package dependency.
Especially it happened if there are tens or hundreds of packages in one state.
Example of the errors:
E03020014: Detected version dependency on the package xxx v2.3.6 in state Test.
E03020014: Detected version dependency on the package xxx v2.4 g in state Test.
E03020011: The package Promote verification failed.
E03060019: Process Execute failed. Process Name: Promote to Release.
Is there a tool to see the whole package dependencies in a state and the details of a selected dependency?
The software CA SCM R12.1 SP3 provides the Package Dependency Report to give more information on dependencies to help identify any problem with the packages.
Information about this Report from the CA SCM R12.1 SP3 Release Notes (page 14):
Support to view Package Dependency Report
This feature lets you view the dependent packages for any package and add the dependent packages, while executing the Promote or Demote processes. This feature verifies that all the dependent packages are promoted together and inconsistency in the code is avoided.
The following components support this feature:
CA SCM Workbench
CA SCM Plug-in for Microsoft Visual Studio and Eclipse
CA SCM Command Line
Note: In the CA SCM Plug-in for Microsoft Visual Studio, Eclipse, and in Command Line utilities, the Package Dependency feature works as described in this topic.
The same behavior is applicable for Demoting Packages.
Release: SCMNCR99000-12.1-Harvest-Software Change Manager-Named User-Competitive Replacem