Helix Core is now P4. Product user interfaces will be updated soon. Learn more >>

P4 Server Administration Documentation | 2025.2

# Changelist server (P4CHANGE)

By default, P4 Servers do not coordinate the numbering of changelists. Each P4 Server numbers its changelists independently. If you are running multiple servers, you can configure your servers to refer to a Changelist server from which to obtain changelist numbers. Doing so ensures that changelist numbers are unique across your organization, regardless of the server to which they are submitted. Any number of servers can refer to a centralized changelist server.

Prerequisite: All outer servers must be at the same (or newer) release level as the Changelist server.

To configure a P4 Server to use a your Changelist server, set ``P4CHANGE`` before starting the second server, or specify it on the `p4d` command line with the `-g` option:

    p4d -g change-server:1666 -p 1999

In this example, the outer server is configured to use the Changelist server, which is named `change-server`. When a user creates a pending numbered changelist or submits a changelist, the outer server contacts the Changelist server to obtain a changelist number.

This configuration has no effect on the output of the `p4 changes` command. The `p4 changes` command lists only changelists from the currently connected server, regardless of whether it generates its own changelist numbers or relies on a Changelist server.

If your server is making use of a Changelist server, the following line appears in the output of `p4 info`:

    ...
    Changelist Server: [protocol:]host:port

Where `[protocol:]host:port` refers to the protocol, host, and port number of the Changelist server.

On Windows, configure the outer server with `p4 set -S` as follows:

    p4 set -S "Outer Server" P4CHANGE=change-server:1666
    p4 set -S "Outer Server" P4PORT=1999

## Remote user or service user

If a service user is configured, that service user is used to contact the Changelist server and obtain the change number. If not, the built-in `remote` user is used. See Example security configuration with remote or service user.

We recommend using a service user.

Your search for returned results