Helix Core Server Administrator Guide: Multi-Site Deployment (2019.1)

Configuring the build farm replica

  1. On the master server, configure the build farm replica server as follows:

    $ p4 server builder-1667

    The following form is displayed:

    ServerID:       builder-1667
    Name:           builder-1667
    Type:           server
    Services:       build-server
    Address:        tcp:builder:1667
    Description:
            Build farm - bind workspaces to builder-1667
            and use a port of tcp:builder:1667
  2. Create the build farm replica server’s server.id file. On the replica server (not the master server), run the following command

    $ p4 -p builder:1667 serverid builder-1667
  3. Restart the replica server.

    On startup, the replica build farm server reads its server ID of builder-1667 from its server.id file.

    Because the server registry is automatically replicated from the master server to all replica servers, the restarted build farm server takes on the P4NAME of buildfarm1 and uses the configurables that apply to a P4NAME setting of buildfarm1.

    Important

    To avoid configuration problems, the value of serverID should always match the value of P4NAME if both are set. We recommend setting serverID, but support P4NAME for backward compatibility.

    In this example, the build farm server also acknowledges the build-server setting in the Services: field of its p4 server form.

    Next step

    Binding workspaces to the build farm replica