Release Notes
Public
9.0.16.4224: May 12 2020
New
All platforms - Server: new adminpwd subcommand added to plasticd!
To set the Plastic server administrator password you can now run the following command:
> plasticd adminpwd --pwd=<new_password>
This replaces the previous method:
> adminconsolepwd --pwd=<new_password>
New
All platforms – All clients and servers: Implemented Cloud organization region server resolution.
We're getting ready for the new cloud2, a greatly improved version of Plastic Cloud!
The new version will feature an entire constellation of servers around the world, not just storage places like in the current cloud.
This means when you try to connect your_org@cloud it won't automatically resolve to server cloud.plasticscm.com but it will retrieve the right server for your region.
We implemented that resolution to get ready for the new Cloud.
New
All platforms - Server: Now the Jet backend allows configuring the max amount of memory used by caches.
When the process reaches the memory limit, it starts to clean the caches of the least recently used repositories. The server will clean the configured percentage of the total number of caches.
By default, there is no memory size limit. You need to configure it to enable this functionality. In that case, the default percentage to free will be 25% (not used unless a size limit is set). You can configure both values can be in jet.conf, using the following settings:
maxcachessizeingb=2 maxcachessizefreepercent=30
Bear in mind that the memory will not be released until the GC runs the next full collection.
Bug
All platforms - Server (.NET Core flavor): Fixed an obfuscation issue that affected the log.
Our custom appender was obfuscated in the .NET Core flavor of the server. This prevented log4net from being able to find it. Now that's fixed!
Bug
All platforms - Plastic, Gluon, Command line: Fixed a broken checkin to encrypted repos if a fragment was bigger than 4MB.
It only happened on encrypted repos (typically Plastic Cloud) and only when a big file compressed in chunks of 4MB had one of the compressed fragments growing beyond 4MB due to the encryption. We never seen that before and it happened to us internally doing a simple checkin of an Excel.
We fixed the issue and should work fine now.