Release Notes

Command-line client: New environment variable to track the merge info during an 'after-clientcheckin' trigger

The after-clientcheckin trigger will now fill a new environment variable named PLASTIC_MERGE_LINKS with info about the merge links (if any) introduced in the checkin operation (i.e. checking in a merge from another branch).

The value of the PLASTIC_MERGE_LINKS environment variable would be like this format (just one merge link):

mergetype:<TYPE_OF_MERGE_LINK>,source:<CHANGESET_NUMBER>@rep:<REP_NAME>@repserver:<REP_SERVER>

And if there are several merge links in the checkin operation, they will be separated by semicolon ';' char:

mergetype:<TYPE_LINK#1>,source:<CHANGESET_NUMBER#1>@rep:<REP_NAME#1>@repserver:<REP_SERVER#1>;mergetype:<TYPE_LINK#2>,source:<CHANGESET_NUMBER#2>@rep:<REP_NAME#2>@repserver:<REP_SERVER#2>

Example:

PLASTIC_MERGE_LINKS=mergetype:merge,source:264@rep:tools_repo@repserver:rainbow:8087

Please refer-to the client checkin triggers documentation site for further info.

Server: New environment variable to track the merge info during an 'after-checkin' trigger

The after-checkin trigger will now fill a new environment variable named PLASTIC_MERGE_LINKS with info about the merge links (if any) introduced in the checkin operation (i.e. checking in a merge from another branch).

The value of the PLASTIC_MERGE_LINKS environment variable would be like this format (just one merge link):

mergetype:<TYPE_OF_MERGE_LINK>,source:<CHANGESET_NUMBER>@rep:<REP_NAME>@repserver:<REP_SERVER>

And if there are several merge links in the checkin operation, they will be separated by semicolon ';' char:

mergetype:<TYPE_LINK#1>,source:<CHANGESET_NUMBER#1>@rep:<REP_NAME#1>@repserver:<REP_SERVER#1>;mergetype:<TYPE_LINK#2>,source:<CHANGESET_NUMBER#2>@rep:<REP_NAME#2>@repserver:<REP_SERVER#2>

Example:

PLASTIC_MERGE_LINKS=mergetype:merge,source:3534@rep:assets_repo@repserver:rainbow:8087

Please refer-to the server checkin triggers documentation site for further info.

All platforms - Command-line client: New 'cm configure' command replaces 'clconfigureclient' tool.

The clconfigureclient tool was a mono/netframework application, and it had troubles configuring a client with a server using ssl on linux and macOS. This was caused due to unmatched security protocol for the ssl connection between the clconfigureclient process and the plastic server.

To fix this, we have removed the clconfigureclient application, and created a subcommand for the regular command-line-client of Plastic SCM (that runs on netcore, and thus accepts enhanced security protocol, enabling a correct ssl handshake with the plastic server).

The new command is cm configure command, and does the same as clconfigureclient application.

Issue cm help configure to show the command help for further info.

All platforms - Gluon: Try the new Gluon GUI!

You are cordially invited to try out the new Gluon GUI, codenamed GluonX. GluonX has all the functionality of Gluon across all platforms, and additionally includes support for changelists in the Checkin view.

To make it as easy as possible, we have added a button to the existing Gluon GUIs which will launch the new GUI. Note, you can switch back at any time using the "Switch to legacy GUI" option in the menu at the top right of the new GUI.

Switch to new GUI on Windows:

Switch to new GUI on Mac:

Switch to new GUI on Linux:

When GluonX is launched you will be presented with this welcome screen:

Switch back to original GUI:

Please give the new Gluon GUI a try and share your thoughts with us.