P4V User Guide (2017.1)

Before you start to work with distributed versioning, it is important to understand certain basic concepts — including distributed versioning architecture and how servers relate to one another in this architecture. Please refer to Using Helix For Disributed Versioning for information on the distributed model.

P4V’s DVCS functionality allows users to create personal servers and submit changes locally without the need to connect or set up a remote server. If the user wishes to clone, fetch or push assets from a remote server, that server must meet the minimum version of 2016.2.1487173 and be set up to accept DVCS commands.