Release Notes
10.0.16.6280: Nov 18 2021
All platforms - Plastic: Triggers no longer wait if parent process has exited and a child process is invoked.
Previously, triggers that launched a child process would wait for it to exit before returning. Now they allow the child process to run in the background while the trigger returns.
Command line client: cm archive command help improvements
Added more information and examples about the required use of the externaldata.conf file when unarchiving (restoring) an archived revision.
New samples:
1) Archive one revision: cm archive Assets/RoofTextures/Textures/Wooden_Roof_05.png --file=/Users/ruben/archive/battle 2) See the archived revision in the specified output path: ls -al /Users/ruben/archive/battle* -rw-r--r-- 1 ruben staff 2220039 Nov 9 10:52 /Users/ruben/archive/battle-100280-167 Unarchive (restore) example: 1) Add the output archive folder to the externaldata.conf file: vi /Users/ruben/.plastic4/externaldata.conf /Users/ruben/archive 2) Unarchive the revision: cm archive Assets/RoofTextures/Textures/Wooden_Roof_05.png --restore
Command-line client: Updated the cm partial add documentation to include the formatting arguments.
Now, the cm partial add help includes the --format and --errorformat arguments. The help shows you how to use these arguments to retrieve the output in a specific format when adding items to a partial workspace.
For example:
cm partial add -R * --format="ADD {0}" --errorformat="ERR {0}"
Command-line client: Updated the cm lock list documentation to include the "machine readable" arguments.
Now, the cm lock list help includes the --machinereadable , --startlineseparator, --endlineseparator, and --fieldseparator arguments. The help shows you how to use these arguments to output the result in an easy-to-parse format.
For example:
cm lock list --machinereadable --startlineseparator=">" --endlineseparator="<" --fieldseparator=","
All platforms Server: New ThreadPool boosting system to avoid long waiting requests
The server allows creating new threads to attend to the requests and goes beyond the max thread limit if needed.
Before this task, the boosting mechanism handles the slow requests (calls running for too long) and the too many requests waiting.
Now it also handles when the request is waiting for too long. It's helpful on the following scenario:
The server receives a high number of requests for a while. It's able to attend almost all of them with the current threads but not all, so the request queue starts growing little by little.
The old mechanism detects it when the queue grows too much. But this new mechanism detects it much earlier, improving the server responsiveness.
All platforms - WebAdmin: Fixed the Lock Rules page
The Lock Rules page in the Plastic server WebAdmin displayed an error. We fixed it, so now you can review/set the lock rules in your on-premises server again.
All platforms - Cloud: Fixed download data operations (update) waiting for other operations to complete.
In the detected case, the download data calls waited for a delete data operation (like removing a changeset) to finish.
This happened because we had a common throttle to limit the number of concurrent operations against the blob storage. Now, each operation type has its own throttle.