Release Notes

Windows - Command line client: netcore-compiled command line client for Windows!

From now on, the command line client (cm) will be a netcore-based application, replacing the netframework-based command line client.

This also unlocks new cm subcommands that were just available for netcore flavor, like cm api subcommand (see release note below).

Enjoy!

Windows - Plastic SCM API: The Plastic SCM API is now embedded in the CLI!

We created a new cm api command that starts the Plastic SCM API. It allows the same arguments as the old plasticapi.exe application (we removed this deprecated executable from the installer).

The previous versions (10.0.16.6419, 10.0.16.6443) already had this cm api command, but just for Linux and macOS. From now on, Windows will have also this command available.

Find more info about it via the command help:

cm api --help

And see more usage details at: https://www.plasticscm.com/documentation/restapi/plastic-scm-version-control-rest-api-guide

All platforms - Plastic SCM API: The Checkin endpoint now supports partial workspaces

We extended the Checkin endpoint in the Plastic SCM API to support partial workspaces. You will now be able to perform checkin operations in a partial workspace using this client-side REST API.

Just launch the cm api command and perform a POST request to endpoint /api/v1/wkspaces/{wkName}/checkin with a JSON body like this:

{
    "paths": ["path-to-my-file", "path-to-another-file"],
    "comment": "my current changes for my task"
}

All platforms - Plastic SCM API: New endpoint to retrieve file info is now available

We created a new endpoint in the Plastic SCM REST API to retrieve information from a file. You will now be able to perform [console]fileinfo[/console] operations in your workspace, using this client-side REST API.

Just launch the cm api command and perform a GET request to endpoint /api/v1/wkspaces/{wkName}/fileinfo/path-to-the-file-to-get-info.

All platforms - Plastic SCM API: The Update endpoint now supports partial workspaces

We extended the Update endpoint in the Plastic SCM API to support partial workspaces. You will now be able to perform update operations in a partial workspace using this client-side REST API.

Just launch the cm api command and perform a POST request to endpoint /api/v1/wkspaces/{wkName}/update.

All platforms - Plastic SCM API: The Switch endpoint now supports partial workspaces

We extended the Switch endpoint in the Plastic SCM API to support partial workspaces. You will now be able to perform switch operations to branch or changeset in a partial workspace using this client-side REST API.

Just launch the cm api command and perform a POST request to endpoint /api/v1/wkspaces/{wkName}/switch with a JSON body like this:

{
    "objectType": "branch",
    "object": "main"
}

All platforms - Plastic SCM API: New revert endpoint for regular and partial workspaces

We created a new Revert endpoint in the Plastic SCM API. You will now be able to perform revert operations in your workspace, partial or otherwise, using this client-side REST API.

Just launch the cm api command and perform a POST request to endpoint /api/v1/wkspaces/{wkName}/revert/{my_item_to_revert} with a JSON body like this:

{
    "changeset": 28
}

All platforms - Plastic SCM API: New partial configure endpoint for partial workspaces

A new Partial Configure endpoint has been added to the Plastic SCM API. Using this client-side REST API you will now be able to perform partial configure operations in your partial workspace.

Just launch the cm api command and perform a POST request to endpoint /api/v1/wkspaces/{wkName}/partialconfigure with a JSON body like this:

{
    "instructions": [
        {
            "path": "/",
            "action": "unload"
        },
        {
            "path": "/",
            "action": "load"
        }
    ]
}

All platforms - Plastic SCM API: New merge endpoint for regular workspaces

We created a new Merge endpoint in the Plastic SCM REST API. You will now be able to perform merge operations in your workspace, using this client-side REST API. This operation doesn't support conflict resolution at the moment.

Just launch the cm api command and perform a POST request to endpoint /api/v1/wkspaces/{wkName}/merge with a JSON body like this:

{
    "sourceSpec": "br:/main/mybranch"
}

All platforms - Plastic SCM API: New endpoint to undelete removed elements is now available

We created a new undelete endpoint in the Plastic SCM REST API. You will now be able to perform undelete operations in your workspace, using this client-side REST API.

Just launch the cm api command and perform a POST request to endpoint /api/v1/wkspaces/{wkName}/undelete with a JSON body like this:

{
    "revSpec": "rev:itemid:4689#cs:23",
    "path": "my_file"
}

All platforms - Plastic SCM API: New create shelve endpoint for regular workspaces

We created a new Create Shelve endpoint in the Plastic SCM API. You will now be able to create a new shelve from changes in your workspace, using this client-side REST API.

Just launch the cm api command and perform a POST request to endpoint /api/v1/wkspaces/{wkName}/shelvesets with a JSON body like this:

{
    "comment": "my amazing shelve comment",
    "paths": ["path-to-my-file", "path-to-another-file"]
}

All platforms - Plastic SCM API: New endpoint to apply shelvesets is now available

We created a new Apply Shelve endpoint in the Plastic SCM API. You will now be able to apply a shelve in your workspace, using this client-side REST API.

Just launch the cm api command and perform a PATCH request to endpoint /api/v1/wkspaces/{wkName}/shelvesets/31 to apply shelve 31.

All platforms - GitSync: main branch support improvements

Now cm sync autodetects if your Git repository uses "main" or "master" as the main branch.

You can explicitly tell it to use any branch as main branch with --mainbranch:

cm sync REPO@SERVER git https://github.com/GITREPO.git --mainbranch=trunk

All platforms - Client: cm update now supports a machine readable format

To obtain an easily parseable output, just use the --machinereadable option:

$ cm update --machinereadable --verbose

<C:/workspace/CreatedDir>
<U:/workspace/UpdatedDir>
<D:/workspace/ModifiedDir>
<C:/workspace/createdfile.txt>
<U:/workspace/updatedfile.txt>
<M:/workspace/modifiedfile.txt>
<D:/workspace/deletedfile.txt>
<SAME_REV:/workspace/untouchedfile.txt> # Only in verbose mode.

Remember you can override the default separators by using formatting options. You might need to double quote them depending on your shell:

$ cm update "--startlineseparator=<" "--endlineseparator=>" "--fieldseparator=:"

All platforms - Client: cm partial update now supports a machine readable format

To obtain an easily parseable output, just use the --machinereadable option:

$ cm partial update --machinereadable

STAGE Plastic is updating your workspace. Wait a moment, please...
STAGE Updated 0 bytes of 41.68 MB (0 of 3 files to download / 0 of 3 operations to apply) /file.txt
...

Remember you can override the default separators by using formatting options. You might need to double quote them depending on your shell:

$ cm partial update "--startlineseparator=[" "--endlineseparator=]" "--fieldseparator=:"

[STAGE:Plastic is updating your workspace. Wait a moment, please...]
[STAGE:Updated 0 bytes of 41.68 MB (0 of 3 files to download / 0 of 3 operations to apply):/file.txt]
...

All platforms - All clients: The status operation performance has been improved by changing how the stats times are tracked (again :).

This is only noticeable in super-huge workspaces (> 4M of files).

The overall time of the status operation is a 15% faster, but this is only noticeable when the watcher is enabled and after the first status run.

In this case, the 'cm status' went from 7.1s to 6s.