Release Notes

Public

11.0.16.8060: Jun 22 2023

New

All platforms: Trim your repository size with Purge

Real-time 3D projects can grow substantially in storage size. The iterative nature of development leads to the creation of multiple revisions of large files that, by design, are kept safely stored in Unity Version Control. Although we keep this behavior as the standard, we also want to provide our customers with flexibility so they can choose how to better manage their data.

We are excited to introduce Purge. You'll have the power to permanently delete those old, unused revisions and trim your repository data, leaving room for the ideas that lie ahead. You'll be able to select a specific period of time and file extensions you want to remove, and in a few steps, you'll get your repository shrunk.

Important note: This operation is destructive and irreversible. While we want to give users the flexibility to have the ability to control their repositories, we also don’t recommend purging your repositories. Unity Version Control is designed to keep the history of your project fully registered as long as it lives, and the use of purge means that you are losing data.

== A feature with safety features in mind ==

While this operation is destructive and irreversible, we designed it to preserve the most vital revisions. This ensures that you will always have stable checkpoints inside your repository.

The purging process calculates the scope of your requests, skipping those revisions loaded at the head of a branch or if they exist in a changeset with a label. These simple safety features guarantee that you can always return to any label or branch head.

== Try now on your CLI ==

Purge is only available through the command-line interface, where you can calculate, execute, and consult the history of your operations. Don’t forget to set permissions for it and to keep it as an administrator-only functionality.

First, you will need to request a purge. This is done using the “cm purge register” command, specifying the file extension and the ‘before’ date when to apply the purge.

> cm purge register ".png" "2023-Jun-21 13:40" --repository=prince
A7919afc-45af-4c58-a5b8-c54c32f1c0ea

The register command will return you a purge GUID, this value can be used to check its status via the “cm purge show” command:

> cm purge show a7919afc-45af-4c58-a5b8-c54c32f1c0ea
PurgeId: a7919afc-45af-4c58-a5b8-c54c32f1c0ea
Repository: prince
Author: manu
Status: ReadyToPurge
Purge size: 77 revisions, 290.06 MB
.png: 77 revisions, 290.06 MB

Once you are sure you want to run the purge operation, you will need to use the “cm purge execute” command, specifying the purge GUID you want to execute.

>cm purge execute a7919afc-45af-4c58-a5b8-c54c32f1c0ea
PurgeId: a7919afc-45af-4c58-a5b8-c54c32f1c0ea
Repository: prince
Author: manu
Status: ReadyToPurge
Purge size: 77 revisions, 290.06 MB
.png: 77 revisions, 290.06 MB

You’ll need to confirm the request to safeguard the process.

This operation cannot be undone or canceled. You will permanently lose the revisions of these files.
Tip: if you want to inspect all the affected revisions, do NOT continue and run this command:
  $ cm purge show a7919afc-45af-4c58-a5b8-c54c32f1c0ea --verbose --server=localhost:8787
Are you sure you want to execute the purge? (y/n)
y
The purge action is now running.

Lastly, you can use the command “cm purge history” to check the specific status of one purge or previously executed purges.

> cm purge history
a7919afc-45af-4c58-a5b8-c54c32f1c0ea PurgeCompleted

== Check out the complete CLI documentation and learn more about Purge ==

Since we are talking about CLI, we recently updated and brought the documentation to the web, making it easy for everyone to find, search, and learn about every available command and the extensive list of capabilities from Unity Version Control.

https://docs.unity.com/devops/en/manual/uvcs-cli/version-control-cli

== How to Access ==

You can visit our webpage and download the latest version right now:

https://www.plasticscm.com/download

Please note that this feature is only available through the Unity Version Control CLI for Cloud customers. Only new Cloud organizations will have the new ‘purge’ permission enabled by default for the “Administrators” group. If you want to start using this feature, make sure you grant the ‘purge’ permission first.

If you are not a customer or want to start using Unity DevOps for free, you can subscribe here:

http://www.unity.com/products/unity-devops

Bug

All platforms - Desktop GUI: Pending merge links were not visible with no pending files

The empty state message was displayed in the Pending Changes view without considering any pending merge links, just taking into account if there were files with pending changes to check-in. Now the empty state message won't be shown when pending merge links are detected.