Release Notes
Public
9.0.16.4345: Jun 19 2020
New
macOS - DevOps: We enabled the DevOps feature in our .NET Core falvor of the server for macOS!
Remember the built-in DevOps feature we bundle in our Plastic SCM Servers out-of-the-box? Well, we lacked of this feature in macOS platform. Wait no more! Now it's available for Mac OS "Server .NET Core installer" & "Server .NET Core bundle".
New
Windows - Plastic, Gluon: Spreadsheet Compare is now the default tool for Excel file diffs!
When you diff Excel files (.xls or .xlsx) in Plastic and Gluon, we now launch Microsoft's Spreadsheet Compare tool by default.
Of course, if you have configured another tool for Excel files, that configuration will be honoured.
Here is a sneak preview:
Launching the tool depends on Plastic being able to find an installed SpreadsheetCompare.exe. We search in:
C:/Program Files (x86)/Microsoft Office/Office16/DCF
C:/Program Files (x86)/Microsoft Office/{UserName}/Office16/DCF
...and also on the PATH environment variable.
So, if you have it installed somewhere other than the above, please add it to your PATH.
Bug
Windows - Plastic: We fixed the "Maximum number of recent comments" preference.
The "Maximum number of recent comments" preference, which sets how many previous comments are seen in the "Checkin comments" drop down of the Pending changes view, is no longer ignored.
Bug
All platforms - Server (Jet backend): The server now releases the locks of an abandoned replication operation.
Now the server can detect which replication operations were abandoned and release their locks after 2 hours.
We consider a replication operation is abandoned when the Plastic client doesn't cancel or finish it. This generally happens because it is killed (e.g. Ctrl+C on a CLI cm push command). It also happens when the operation fails due to the error "The LDAP token expired".
Bug
All platforms - Server (.NET Core flavor): The server can now handle the db.conf configuration file again.
A code obfuscation oversight rendered the Plastic server unable of reading the db.conf file on startup, giving a null reference error. That's now fixed!