Release Notes
Public
8.0.16.3079: Mar 19 2019
New
Command line client: the cm replicate command is now deprecated. It is replaced by push and pull, in an effort to make it easier to use, and improve the semantics of the command line.
These commands are now equivalent:
cm replicate br:/main@project@remote:8087 project@local:8087 cm pull br:/main@project@remote:8087 project@local:8087 cm replicate main@project project@remote:8087 --push cm push main@project project@remote:8087 cm replicate main@project --package=project.package cm push main@project --package=project.package cm replicate project@localhost:8087 --import=project.package cm pull project@localhost:8087 --package=project.package cm replicate main@project@remote:8087 project --nodata cm pull main@project@remote:8087 project --nodata cm replicate hydrate project cm pull hydrate project
The authentication options (--authmode, --authdata, --authfile, --user, and --password), and the translation options (--trmode and --trtable) work exactly the same as before, both for pull and push.
The deprecated replicate command is still available if you call it, but we recommend you to migrate any automation or script that relies on it to the new push and pull.
In any circumstance, we will warn you through the release notes when the replicate command ceases to exist.
Bug
Plastic GUI: The replication source aliases in the Branch Explorer view were lost when the GUI closed. We fixed that to make them persistent.
Bug
WebAdmin: The DevOps dashboard didn't work if the Plastic SCM Server owner was a group. Now it's fixed.
Bug
CLI: The 'cm listlocks --onlycurrentworkspace' command used the workspace name instead of the workspace ID to filter the locked files. This caused issues if two developers had workspaces with the same name. We fixed the code to use the workspace ID in the lock filter and prevent collisions.
However, this change will only affect locks created with this version or higher, so don't be alarmed if you don't see any changes in the 'cm listlocks --onlycurrentworkspace' output immediately. As a side effect, old clients will see the workspace ID in the command output as part of the workspace name for locks created with a newer client version, example:
e9f49aaf-c803-4639-8639-d71037d9d57d Borja wk:f09a621f-a16c-47f4-b60e-b864cb3d65ba /art/body.jpg
Bug
History commands (CLI history command and History View in GUIs) didn't check permissions. As a result, all revisions were displayed regardless of what permissions the current user was granted. We fixed this issue so that users will only see revisions from branches available to them, according to their permissions.