Release Notes

Public

10.0.16.6179: Oct 27 2021

New

All platforms - CLI: Now you can specify tokens and cloud region configuration for every command

We added new global parameters to the CLI. They allow you to tune the configuration tokens and cloudregions files to use for command execution. So you don't need to have them configured on the machine. It's useful for integrations where there is no previous configuration.

The new parameters are:

* --tokenconf=[token_conf_path] - allows specifying the token file to use for the command execution.

* --cloudregionsconf=[cloud_region_conf_file] - allows specifying the cloudregion file to use for the command execution

Example execution:

cm repo ls --clientconf="C:\mysharedconf\client.conf" --tokensconf="C:\mysharedconf\tokens.conf" --cloudregionsconf="C:\mysharedconf\cloudregions.conf"

New

All platforms: Change password in User/Pass auth mode is now instant.

Prior to this version, changing user's password in User & Pass authentication mode required up to 5 mins to be updated in the server.

From now on, changing a password is immediate. If the password is changed in the server, just open the "Preferences" > "General" window in your Plastic SCM client and enter the new password.

REMARK: A credentials prompt could be shown in the Plastic SCM client under the following conditions:

* Your client is configured/connected to a server in User/Password mode.

* Your client has also a persistent server profile to connect to the same server.

* Then, your password is changed in the server.

This could happen because credentials of persistent profiles have preference over the client configuration. To avoid this prompt dialog showing up again and again, we encourage to enable the "Remember credentials as a connection profile" checkbox on that dialog, so the credentials of the stored profile are properly updated.

New

All platforms - Server: The warmup of a server under heavy load has been improved by x20 when using the UP authentication mode for groups.

This is valid when using the UP authentication mode or the mixed LDAP + UP groups mode (in both, the groups are read from the groups.conf file).

The bigger is the number of groups and users/groups inside these groups, the more noticeable is the performance improvement. The x20 improvement has been measured using 12000 group entries.

New

Linux - Proxy: the "plasticscm-proxy-server" is now the default proxy package, netcore-based.

We renamed the "plasticscm-proxy-server-netcore" to just "plasticscm-proxy-server", and we removed any plastic proxy compilation based on mono stack.

So, to install the proxy, use this package name from now on: "plasticscm-proxy-server".

REMARK: some distros (centos, opensuse, fedora) could require the removal of legacy "plasticscm-proxy-server-netcore" package before installing the new one. If so, please remove the "plasticscm-proxy-server-netcore" on your package manager before installing the new "plasticscm-proxy-server" (the legacy configuration is kept during the upgrade)

Bug

Windows - plasticfs: Updating a workspace to the head of the branch with changes in the workspace discarded said changes.

This scenario is more likely to happen when you are working on a branch with a colleague. They do a change, check it in, and then you update your workspace to grab the change. In a static workspace, you get to keep your workspace changes (both local and controlled), and even merge your changes with the incoming ones if needed! In a dynamic workspace, we were overriding your workspace changes. Not anymore, now both static and dynamic workspaces behave the same way.

Bug

All platforms - Web UI: Fixed a bug where if you had an assigned review you'd see an empty list when going to the code reviews page.

Bug

Linux - Installers: Aesthetic fix: removed confusing warning message while installing the client

The package installer in the supported Linux distributions printed this message when it processed the dependency package 'plasticscm-certtools-mono4':

Could not resolve host 'cloud.plasticscm.com'

The package post-install script pre-populates the Mono certificate store from Plastic SCM trusted domains. One of those was 'cloud.plasticscm.com', which is now deprecated.

This error didn't prevent the package from completing the installation, but it could alarm users. Now the message won't appear anymore, and the package imports the certificates from the proper domain (plasticscm.com).

Bug

All platforms - Plastic, Gluon: Fixed 'Selector can't locate a revision for the item xxx' error when checking-in local changes (changes done outside Plastic).

The problem was related to moving a controlled file into a private folder. The issue could be reproduced as follows:

1. Create in disk a workspace with the below file structure and check it in.

/Assets/Folder1
/Assets/Folder1/Folder2
/Assets/Folder1/Folder2/Folder3
/Assets/Folder1/Folder2/Folder3/New Material.mat
/Assets/Folder1/Folder2/Folder3/New Material.mat.meta
/Assets/MoveTo

2. In Windows Explorer, move the folder /Assets/Folder1/Folder2/Folder3 to /Assets/MoveTo.

3. Edit the content of the file/Assets/MoveTo/Folder3/New Material.mat.meta.

4. Try to checkin the current pending changes from the Plastic GUI.

Bug

Windows - plasticfs: Updating a workspace to the head of the branch with changes in the workspace discarded said changes.

This scenario is more likely to happen when you are working on a branch with a colleague. They do a change, check it in, and then you update your workspace to grab the change. In a static workspace, you get to keep your workspace changes (both local and controlled), and even merge your changes with the incoming ones if needed! In a dynamic workspace, we were overriding your workspace changes. Not anymore, now both static and dynamic workspaces behave the same way.

Bug

All platforms - Web UI: Fixed the following issues

- Not seeing the repository name in the breadcrumb navigation

- The menu not being selected when clicking on an item in a list e.g., when viewing the code review details.

Bug

macOS - Plastic: Fixed the revisions displayed in the code review

Under some circumstances in the code review, when you switch between the review modes or changesets the revisions displayed for the selected file in the diff viewer were not the correct ones. We fixed it, and now you will see the correct differences.

Bug

All platforms - GitSync: Fixed the parsing of LFS pointers that don't end with '\n'.

If (somehow) you have a LFS pointer in a wrong format (without the ending '\n') in your repo, now, we support it too!

This link shows the specification of the LFS pointers and how every entry has to end with '\n'.

Bug

All platforms - Web UI: Fixed image preview being stretched in code reviews