IPLM Core version 3.5.0

Release date: June 8, 2023

Enhancements

  • [CLI-645] (Case Number 00740411) - Retained Workspace Alias

    • pi update without a provided FQN target will make more intelligent choices regarding user intent as to the update target. If the current top level was last loaded at or updated to an alias, pi update assumes that the user intends to update to that alias, even if the alias is no longer set on the top level IPV. Unique aliases are now supported in this mode as well. See IPV target definition for more information.

    • The output of pi ws status now reports the default pi up target currently in effect, which is the version/alias of the top level IPV in the workspace that will be assumed when pi update is run without an explicit target.

  • [CLI-648] (Case Numbers 769417, 780986) Workspace update verbose mode

    • pi update now supports a --verbose flag that reports the file level updates that result from the update. P4 and SVN type IPs are supported. IPVs that are fully removed from the workspace or newly added to the workspace will not report file level updates when the --verbose flag is provided, because all of their files are being added or removed. See Viewing workspace modifications for more information.

    • The pi update --verbose flag can be combined with the --dry-run flag to report the file level changes that would result from the update, without actually performing the update.

    • SVN type IPs will now run in --non-interactive mode and report any file level conflicts that result (or would result in --dry-run mode) from the update operation.

    • pi update --verbose commands run on @HEAD IPVs in PiCache correctly reports file level updates in both STATIC_HEAD and default mode.

Known issues

The PiCache IPV Auto Clean Up feature will not work for the static HEAD versions in the cache. Until this is addressed, manual cleanup of these IP versions will need to be done.