Unity Version Control 11.0.16.7665

Command-line client: Update command improved for automation

Command-line client: Several adjustments have been made to the update command:

Command-line client: Before:

Command-line client: Now:

All clients: Incoming Changes respects the cloaked rules.

All clients: Before, the Incoming Changes operation downloaded the files/directories although they were under cloaked paths. This was inconsistent with the update operation behavior and with the cloaked semantics themselves.

All clients: Now, the changes under cloaked paths are skipped like the update operation does.

All clients: The Gluon Incoming changes is not affected by this behavior (cloaked rules don't make sense in Gluon) since the operation works in a different way.

All Platforms - DevOps: Jenkins plug now shows the link to the build job

All Platforms - DevOps: The Jenkins plug now notifies the URL to the build job. This way users are able to get the details about what failed while building the task in Jenkins.

All Platforms - DevOps: Find below a sample of this notification using a local Jenkins plug with a TrunkBot mergebot on Slack:

Command-line client: Switch command improved for automation

Command-line client: Several options have been added to the switch command, mirroring the update command: --silent, --verbose, --xml and --encoding.

Command-line client: See --usage for details:

Command-line client: Undo controlled changes and preserve local content

Command-line client: Added the option -k | --keepchanges to the cm unco & cm partial unco to allow undo checkout and preserve all local changes.

Command-line client: It could be very useful when you have a checked-out file with some changes for testing that you don't want to check in. So, now, you can undo the checkout (that releases the lock), and preserve local changes just to continue with your local tests.

Command-line client: The unco -k command can be applied to all kinds of controlled changes, turning them into local changes. This is complementary to using the checkout command to promote local changes into controlled ones.

Command-line client: Note this option is incompatible with dynamic workspaces.

All platforms - Plastic, Gluon: Improved app stability

All platforms - Plastic, Gluon: We've improved app stability in some scenarios, preventing the app from crash when an exception is thrown

Command-line client: Update --xml now includes deleted items

Command-line client: Before, the --xml output of the update command was meant to only report items with added or updated revisions.

Command-line client: Deleted items are now included:

All platforms - Plastic: Disabled Semantic History option for unsupported text files

All platforms - Plastic: We've disabled Semantic History menu option in Annotate View for all unsupported text files in semantic history (for example, .txt files)

macOS - Plastic: Removed mono-based GUI's

• macOS

macOS - Plastic: We finally removed the mono-based GUI's that were deprecated months ago, in favor of net(core) based counterparts: `plasticgui` and `gluon` .

• macOS

macOS - Plastic: This way we ease the setup of the Plastic SCM GUI applications, since no more "mono/xamarin" and related dependencies will be a requirement anymore.

• macOS

Using the --xml option was not meant to be used in a pipeline.

Using the --silent option was meant to trim all output.

Using the --xml option with no file implies --silent. Informative output gets trimmed.

Using the --silent option removes informative output only. Warning and error messages are still written through standard error output. You can silence those messages by using output redirection.

Added are left as private

Checked-out are left as changed

Deleted are left as locally-deleted

Moved are left as locally-moved

All platforms - Plastic: Fixed exception in diff when selecting files outside of refactor group

All platforms - Plastic: We fixed an error that was causing an exception to be thrown when selecting an item in the diff window that is not inside a refactor group.

Command-line client: Unrelated conflicts when applying a shelve.

Command-line client: The 'shelveset apply' command could show some directory conflicts that were not related to the changes/paths specified in the command.

Command-line client: This happened when 1) only some changes were specified to be applied from the shelveset and 2) there were more than one directory conflicts involved in the shelveset application.

Command-line client: The problem came because the filter used to apply only the specified changes was not applied again after resolving a directory conflict. Fixed.

Command-line client: Update command --xml and --silent options are incompatible

Command-line client: Before, using the --silent option allowed the XML output to be printed but affected to the contents themselves.

Command-line client: Now, those options are compatible. Moreover, the --xml option now implies --silent.