Release Notes

The Unity Version Control CLI documentation is now live on the web!

Previously, we were missing the complete documentation with all commands, and the only way to access it and understand how to use the command line was through internal help. Now there’s a comprehensive guide available for everyone!

You can find the documentation here:

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

It’s packed with detailed explanations, examples, and usage instructions for all the Unity Version Control CLI commands. Whether you’re a seasoned pro or just getting started, this resource will be invaluable.

Keep in mind that this is the first published version. While it’s a significant milestone, we recognize that there’s always room for improvement.

Stay tuned for more updates on the online CLI help!

All-platforms - Command-line client: New mvbranch trigger

We added a new type of trigger, which is called before/after the renaming of a branch. Along with the trigger, we added two new environment variables:

PLASTIC_BRANCH_NEW_NAME
PLASTIC_FULL_BRANCH_NEW_NAME

These can be used in combination with previous environment variables for automation purposes (see below).

For instance, it would be possible to create a trigger with the following command:

cm trigger create before-mvbranch MyTrigger "C:\cisystem\trigger.bat C:\cisystem\triggerresult.txt"

This script could contain the following - indeed, you can try something like this to set the trigger up and test it!

REM trigger.bat
@echo off

(
echo PLASTIC_BRANCH_NEW_NAME %PLASTIC_BRANCH_NEW_NAME%
echo PLASTIC_FULL_BRANCH_NEW_NAME %PLASTIC_FULL_BRANCH_NEW_NAME%
echo:
echo PLASTIC_BRANCH_NAME %PLASTIC_BRANCH_NAME%
echo PLASTIC_FULL_BRANCH_NAME %PLASTIC_FULL_BRANCH_NAME%
echo:
) >> %1

And then, when executing a rename in the branch, the result file would have the following content:

# triggerresult.txt
PLASTIC_BRANCH_NEW_NAME = task002
PLASTIC_FULL_BRANCH_NEW_NAME = /main/task002

PLASTIC_BRANCH_NAME = task001
PLASTIC_FULL_BRANCH_NAME = /main/task001

As always, the usual environment variables are also available when running the trigger:

PLASTIC_BRANCH_NAME
PLASTIC_FULL_BRANCH_NAME
PLASTIC_REPOSITORY_NAME
PLASTIC_COMMENT
PLASTIC_USER
PLASTIC_CLIENTMACHINE
PLASTIC_SERVER