Release Notes

All platforms - PlasticX: New GUI Announcement

You're invited to check out the new Plastic GUI - a sneak peek at the work we've been doing to continuously improve the Plastic experience for all users, regardless of experience level. The new Plastic GUI is now the default GUI for MacOS and Linux. It is also discoverable in the bottom left corner of the Windows GUI.

This new GUI is cross-platform, includes a dark theme and provides better syntax highlighting. Many more improvements are coming soon, including Gluon support! Try out the new experience and switch back to the Legacy GUI at any time.

To try out the new GUI simply click on the "Switch to new GUI" text near the bottom of the side panel, as shown in these screenshots:

Switch to new GUI button Linux:

Screenshot

Switch to new GUI button macOS:

Screenshot

Switch to new GUI button Windows:

Screenshot

Welcome to new GUI:

Screenshot

You can switch back to the legacy GUI at any time by selecting the option shown here:

Switch to legacy GUI:

Screenshot

Command-line client: Updated the Spanish command-line help for several commands.

We keep on updating the Spanish documentation of the command-line help. These are the commands whose Spanish documentation has been completely updated on this round:

* log

* ls

* manipulateselector

* merge

* attribute create

* attribute delete

* attribute edit

* attribute rename

* attribute set

* attribute unset

* branch create

* branch delete

* branch history

* branch rename

* branch showmain

* branch showmerges

* repository

* repository add

* repository create

* repository delete

* repository list

* repository rename

* trigger

* trigger create

* trigger delete

* trigger list

All clients: The performance of the status operation was improved again!

The overall time of the status operation is a 60% faster. This is only super-noticeable with huge workspaces (>4M of files), when the watcher is enabled and after the first status runs. Otherwise, the time spent in disk operations makes the improvement less noticeable.

After all the improvements done, the status time goes from 7.1s to 2.7s!

The tests were done:

* using a workspace of 4011530 files, 264143 directories and 264 GB.

* in an e2-standard-8 (Google Cloud) instance with a debian-10 image and a SSD persistent disk.

Command-line client: Changelist info is displayed along with the controlled changes in status command

When using --changelist options in status command, now it shows at the top of every grouped section of changes the information regarding the changelist owning these changes. The "--machinereadable status" option now works along with --changelist.

For instance: considering a workspace with two files (BoxCollider.cpp, and StartGameBtn.cpp), each one added to its corresponding changelist (Physics, GUI), the following command:

cm status --changelist=Physics

Will display something similar to this as far as there is a controlled change in BoxCollider.cpp file:

/main@VideogameEngine@localhost:8084 (cs:1 - head)

Changelist: Physics:Every change related to physic calculations in the engine
Changed
Status         Size       Last Modified    Path
Checked-out    7 bytes    4 minutes ago    BoxCollider.cpp

And the following command...

cm status --changelist=Physics --machinereadable --fieldseparator=_ --startlineseparator=. --endlineseparator=,

.. will display something similar to this as far as there is a controlled change in BoxCollider.cpp file:

.STATUS_1_VideogameEngine_localhost:8084,
.CHLIST_Physics_Every change related to physic calculations in the engine,
.CO_C:wkspacesVideogameEngineWKBoxCollider.cpp,

Command-line client: Allow creating multi-line comments

Allows the use of the escape sequences 'n' and 'rn' to be used in checkin comments to generate line returns. Previously these would not be interpreted as escape sequences and would be included literally in the comment.

Command-line client: Allow the '--xml=output_file' parameter in the 'cm find' command.

Before, you needed to specify '--xml --file=output_file' to print the find result to a file. Now, you can just use '--xml=output_file' like other commands do.

All platforms - DevOps: Trunkbot auto enqueue branches when new changes in dst branch.

Before this version, if new changesets reach your trunk branch (i.e., '/main' branch) while a merge changeset -changes of your own branch and the trunk branch- is being built & tested, it won't be possible to merge the branch.

Now you can set up your Trunkbot configuration to queue the affected branch again automatically, and hence repeating all the branch processing, including the last changes from trunk branch in the merge changeset.

You can enable this feature in the mergebot configuration:

Screenshot