Preface
This guide tells you how to use the distributed versioning features of Helix. Distributed versioning allows you to work disconnected from a shared central server. If you’re new to version management systems, you don’t know basic Helix concepts, or you’ve never used Helix before, read Introducing Helix before reading this guide.
What’s new in this guide for 2015.2
This section provides a list of changes to this guide for the Helix Versioning Engine 2015.2 release. For a list of all new functionality and major bug fixes in Helix Versioning Engine 2015.2, see the Helix Versioning Engine 2015.2 Release Notes.
Seamless login to remotes |
Previously, to log into a shared (remote) server, you had to remember its
For more information, see the section "Forward login to shared server" in “Understanding Remotes”. |
Triggers available for pushing, fetching, and unzipping |
You can now use triggers with the |
New items copied from server to server |
Previously, fetching, pushing, zipping, and unzipping copied the following to the target server:
These commands now also copy the following to the target server:
|
|
The |
Tangent depot |
This release introduces a new depot type — the tangent depot — which is a
system-generated, read-only location in which the |
Consistent cross-server Unicode and case sensitivity |
The new |
|
The remote spec has a new |
Global changelist id and |
The Helix Versioning Engine now has the concept of a global changelist
identifier (ID), which is implemented using the new For more information, see Track a changelist’s identity from server to server. |
New |
You can now distinguish between who owns a changelist and who fetched, pushed, or unzipped it. For more information, see Track who pushed, fetched, or unzipped a changelist. |