Release Notes

Public

 8.0.16.3552: Sep 16 2019

New

All platforms - Command line client: we changed date format in XML output. It was inconsistent across different commands, so we unified it and made it compliant with ISO 8601 (without decimal places).

These are the affected commands:

find
history
log
ls
status
update

If you use or develop any script or integration that rely on these commands, please make sure it still works before updating your production environment.

You can still manually override the date format though. The 'cm find' command accepts a '--dateformat' flag. For other commands that do not accept the '--dateformat' flag, you can add the OutputDateFormat to your client.conf file. For example:

<OutputDateFormat>dd/MM/yy HH:mm</OutputDateFormat>

New

All platforms - Plastic, Gluon: We got some important feedback about how many of our users add their files to source control.

Emulating the usual initial steps in other popular VCSs, one of the first steps a Plastic SCM user does after creating a new repository is adding a ignore.conf file prepared for the project they are going to work with.

Then, they start adding files to source control, but because private files are unchecked by default in the pending changes, this workflow is error prone.

We have addressed that way of adding files adding a new preference - in the Pending Changes (Plastic) and Checkin (Gluon) views, under the Options dialog > What to show, now you can set private files (private and private-added, but not private-ignored) to be selected for checkin by default.

Hope you don't have to write any more "Files I forgot in the previous changeset" checkin comments!

New

Windows - Plastic: A few usability improvements applied to the new Code Review system, designed to encourage users to use the new 'Changes and Questions' system instead of the old regular review comments.

* 'Request a change' is set as default option when adding a new comment.

* Allow users to choose the comment type in the replies too.

* The review comment summary at the bottom of the window shows only first level regular comments, not the replies. Except for 'Changes and Questions' that will continue appearing on their lists even if they are replies.

* The comment navigation now marks as selected the comment and scrolls to it in the comment panel in order to make it more visible.

Remember, right now, you need to launch the application with "plastic --codereview" to enjoy the new feature.

New

All platforms - Gluon: No more surprise massive downloads when you configure your workspace. We've added a handy text box to the configuration window which tells you exactly how many files, and how many bytes, your configuration change will download.

Here are some screenshots for Windows:

Linux:

and Mac:

New

All platforms - Command line client: the subtractive and cherrypick merges can now use the --keepsource and --keepdestination flags to automatically choose a contributor! Before, the subtractive was ignoring these flags.

Imagine that you want to undo a change in a file that was introduced in a changeset along with other changes. These flags are useful to pinpoint only the changes you want to undo.

For example, imagine both file_A.txt and file_B.txt were changed in cs:4, and have more changes afterwards. We only want to undo changes introduced in cs:4 for file_A.txt, while preserving file_B.txt. How can we achieve that?

$ cm merge --subtractive cs:4
The file /file_A.txt needs to be merged from cs:3 to cs:5 base cs:4. Changed by both contributors.
The file /file_B.txt needs to be merged from cs:3 to cs:5 base cs:4. Changed by both contributors.

$ cm merge --subtractive cs:4 /file_A.txt --merge
// Solve merge conflicts…

$ cm merge --subtractive cs:4 /file_B.txt --keepdestination --merge
// No merge conflicts to solve…

$ cm merge --subtractive cs:4
No merges detected

$ cm ci -c="Subtractive keeping file_B.txt!"

Bug

DevOps: Trunk-bot with Jenkins-plug: Since public release 8.0.16.3442, the cm undo command became user-interactive when the workspace is loading a deleted shelveset. This scenario could happen if you have a repo configured with DevOps feature (trunk-bot and jenkins-plug), causing unexpected "build failed" in some builds launched in Jenkins. Now it's fixed.

Bug

Windows - Mergetool: The mergetool contributor shortcuts (Ctrl+1, Ctrl+2, Ctrl+3) didn't work as expected if you opened a diff window (e.g. double-clicking a branch in the Branch Explorer) and then you performed a merge. They were toggling the contributor change twice. It's fixed now.

Bug

Windows - Mergetool: Saving changed files when the diff is editable (i.e. the destination revision is the one loaded in the workspace) displayed a null reference exception message if there wasn't any selected items in the changed files tree. It's fixed now.