Using Helix for Distributed Versioning (2016.2)

There are distributed versioning scenarios in which you want to fetch and push from/to multiple shared servers and you need to use a different Helix identity for each server. You can specify the identity Helix should use for a particular shared server in the RemoteUser field of that shared server’s spec. The p4 fetch and p4 push command then use that identity for authentication against that shared server.