Release Notes

All platforms - Server: Backup prototype.

We're working on a new version of Plastic Cloud, code named cloud2, and we've created a way to backup repositories to cloud, that will be soon available in any on-premises server too, as long as you configure a certain cloud bucket to contain the backup. It supports Amazon, Azure, and soon Google Cloud Storage.

It will work this way. I hope you find it interesting!

All platforms - Server: We implemented a smart scheduling algorithm for backups.

Now that on-premise servers will be able to do cloud-based backups, it would be nice that backups executed automatically, wouldn't it? The issue is that you can't back up a file somebody is writing to at the same time. So backups block repository write operations.

But what happens if you are using your repository, and the Plastic SCM server blocks write access to it? I'll bet you would be sad. Even angry!

We implemented an somehow intelligent system to decide the best time to execute a backup. It is based on the write activity for the last seven days. If you and your team are regular human beings, the backups will probably be scheduled at night time, but if you are night owls, backups will be scheduled to execute at day time. Good enough to get out of your way!

All platforms - Server: connection strings and keys now obfuscated in logs.

We now obfuscate your Amazon S3 connection keys and Azure connection strings before we write the database configuration settings to the log file. This means you can safely share your logs with our Support Team without divulging this private data!

All platforms - clconfigureclient: no need to set port when configuring cloud servers.

When validating the command line arguments for clconfigureclient, we would return failure if the port was not specified, even for cloud servers. The port is not required for cloud servers, so now we don't require the port argument in this case.

All platforms - Server: for LDAP users, Plastic now functions correctly when the LogonWorkstations parameter has been set on the AD server.

Unity plugin: Now, the local project packages are considered for versioning. This feature is available for Unity 2019.3 or later.

This means their folders and contents will appear in the 'Pending changes' view of 'Version Control' window in Unity when they contain any change.