Helix4Git Administrator Guide (2019.1)

Upgrading Git Connector

Upgrading to version 2017.2 from the 2017.1 patch

  1. Verify the Git Connector server id, which, for this example, is my-gconn-centos6:

    *p4 servers*

    The response is similar to:

    my-gconn-centos6 connector git-connector ' This GitConnector service was configured on [Tue Aug 29 10:21:30 PDT 2017] by user [super]

  2. Make sure that you provide the value of the serverid when upgrading the Git Connector:

    configure-git-connector.sh --upgrade --serverid my-gconn-centos6

Here is an example:

sudo /opt/perforce/git-connector/bin/configure-git-connector.sh --upgrade --serverid my-gconn-centos6
hostname: Unknown host

Summary of arguments passed:
...
GitConnector SSH system user       [git]
Home directory for SSH system user [/home/git]
SSH key update interval            [10]
Server ID                          [gconn-gconn-centos6]
GitConnector hostname              [(not specified)]

For a list of other options, type Ctrl-C to exit, and then run:
$ sudo /opt/perforce/git-connector/bin/configure-git-connector.sh --help
...
Would you like to perform the upgrade of this GitConnector instance? [no]: yes
...
Moving existing configuration file to 
/opt/perforce/git-connector/gconn.conf.bak
Writing GitConnector configuration file
This GitConnector instance has been successfully upgraded.

Upgrading helix-git-connector that is prior to the 2017.1 patch

If you have a version of the Git Connector that is prior to the 2017.1 July patch, and you want to use Gerrit, upgrade the package and re-run the package configuration script.

  1. Run:
    UbuntuCentOSSUSE Linux Enterprise Server

    $ sudo apt-get update

    $ sudo apt-get install helix-git-connector

    $ sudo yum install helix-git-connector

    $ sudo zypper install helix-git-connector

  2. Optionally, if your Helix server configuration has changed, or you encounter problems, run the configuration script:

    $ sudo /opt/perforce/git-connector/bin/configure-git-connector.sh

    The configuration script:

    • warns you about the existing configuration file
    • prompts you for P4PORT, super user's account name, and super user password
    • updates the HTTPS and SSH authentication configurations