Using Helix Core Server for Distributed Versioning (2019.2)

Read this first

In order to fetch from or push to a shared server, the case sensitivity of your personal server must match that of your shared server. When you run p4 init, Helix server attempts to set the case sensitivity of your personal server to match that of the shared server specified in your current P4PORT setting.

If you know which shared server your personal server will be fetching from and pushing to, run p4 init -p, passing in the address of the shared server. This tells the Helix Core server to discover the shared server’s case sensitivity and Unicode support settings and apply them to your personal server; this makes the two servers compatible.

If Helix server can’t discover a shared server, the p4 init command will fail. You must then run this command:

$ p4 init -Cx

where C0 sets the server to case-sensitive and C1 sets it to case-insensitive; set the option to match the case sensitivity of the shared server with which you’re communicating.

Similarly, in order to fetch from or push to a shared server, the Unicode support of your personal server must match that of the shared server. When you run p4 init, Helix server attempts to set the Unicode support of your personal server to match that of the shared server specified in your current P4PORT setting. If Helix server can’t discover a shared server, Unicode support defaults to off. If you later want to turn Unicode support on, you can run this command:

$ p4d -xi -r /users/username/dvcsdir/.p4root