Release Notes

All platforms - PlasticX: New Details panel in Workspace Explorer

The Details panel has been added to the right side of the Workspace Explorer in PlasticX. This panel contains the image preview and properties of the selected item in the workspace tree, so it will be refreshed on every new selection. It is a collapsible panel, by default it's collapsed and can be expanded by using the new button "Show details" at the top right.

All platforms - PlasticX: Added comments auto-text feature

We added comments auto-text feature to Plastic. This allows the user to use predefined variables (Date, UserName, Branch Name) or a custom string in the comments textbox in Pending Changes view:

Also, the icons in Preferences Window were updated.

Command-line client: Upgraded changelist command now allows specifying files for the name and the description.

Changelist command has been upgraded with new verbs for management ("create" and "delete" substituting "add" and "rm"). Now it is possible to use new options in changelist commands: --namefile, --descriptionfile, --newnamefile. These options allow to replace the literals used to specify the name of the changelist or its description and to use a path to a file containing the changelist name or description instead.

For instance

cm changelist add "Physics-related changes" "Changes related to the game world environment and the implemented physics"

Could be updated to

cm changelist create "Physics-related changes" --descriptionfile="desc.txt"

Or also could be updated to

cm changelist create --filename="name.txt" --descriptionfile="desc.txt"

Or you could also rename a pre-existing changelist with something like the following:

cm changelist edit --filename="name.txt" rename --newnamefile="newname.txt"

Bear in mind:

- Old command syntax is still working but tagged as deprecated and the help has been updated. If you have automated scripts using this command, they will work, but we encourage you to update those and test the new amazing functionalities

- You can still use the same literals or use the options, whatever the combination that best suits your needs (options + literals, literals + options, all options, all literals).

- The --namefile and --newnamefile options do not allow invalid files or content (non-existing file, empty or multilined texts); in addition, if an non-existing file is supplied to --descriptionfile, it will also fail, but no content validity will be done.

DevOps: Remove branches from Trunkbot processing queue

If you accidentally set the status attribute to a branch, your Trunkbot might enqueue it and eventually merge it.

Before, you could remove it from the processing queue by changing the value of the attribute to something else. Now, removing the attribute from the branch will have the same effect.

Server: Edit cset comment now checks branch perm

When you edit the comment of a changeset, the “change comment” permission needs to be set in the branch that contains the changeset.Before this change, the repo permission was checked, which wasn’t as good solution as checking the permission in the branch.

All platforms - PlasticX: Remark current working item

The bold text style has been applied to the current working item, for the "Name" column of the Changesets and Branches views tables, in order to indicate which item on the list is currently loaded.

Command-line client: Configure data encryption for remote servers

As the owner of a Plastic server, you can configure encryption when trying to pull data from repository inside a remote encrypted server for the first time.

This was true for the Plastic GUIs, but now it is also possible within the command line:

> cm pull br:/main@donuts@homer@cloud dotnuts@marge:8084
...
The 'homer@cloud' source server requires data encryption.
Your server (aka 'marge:8084') is not yet configured to handle encrypted data from it.

Remarks:
* Be very careful with the encryption password; it's the only way to decrypt your data on 'homer@cloud'.
* If you're decrypting data and you enter a wrong password, the data will fail to decrypt and you will have to edit cryptedservers.conf on your server to fix it.
* Be careful to use the same password (encryption key) company-wide to work with 'homer@cloud'. Otherwise, data will be encrypted differently in each server.

Enter a password to generate the encryption key (leave empty to cancel):
***********

Encryption configuration added for server 'homer@cloud'.
...