Perforce TeamHub configuration

Overview

You, the administrator of Perforce TeamHub and the Git Connector of P4 Server, can set up mirroring a Git repository into the P4 Server. You can choose the type of event that causes mirroring to occur:

For details on setting up continuous integration (CI) builds with Jenkins in Perforce TeamHub, see Configuring builds with Jenkins in the Perforce TeamHub User Guide. Note that the feature branch workflow in TeamHub requires a successful (green) build from Jenkins before you can merge the feature branch into the target branch in Perforce TeamHub.

See also CI builds with Jenkins.

Sequence of events

  1. An end-user does a git push from the local computer to the Perforce TeamHub server.
  2. The user's action fires a Repository Webhook in Perforce TeamHub to notify the Git Connector.
  3. Git Connector fetches the new changes.
  4. Git Connector mirrors the Git repo into the specified P4 graph depot.
  5. Optionally, an automated build occurs, using a tool such as Jenkins, which is supported by p4Jenkins.

Limitations

This use case is for Perforce TeamHub on-premise, not the cloud version of Perforce TeamHub.

Repo access is through username/password or SSH key. Perforce TeamHub on-premise does not support for SSO or two-factor authentication.

For mirroring, use a repository hook, not a company hook or a project hook. For details, see the Perforce TeamHub User Guide on Webhooks.

Authentication

Both HTTP and SSH are supported. To use SSH, the public key needs to be added to Perforce TeamHub.

System requirements

  • Ubuntu 14.04 LTS, Ubuntu 16.04 LTS, CentOS or Red Hat 6.x, CentOS or Red Hat 7.x
  • Must be an administrator for a working Perforce TeamHub, so that you can set up a Repository Webhook
  • Must be an administrator on the Git Connector server, so you can run the command to add a mirror hook
  • A working Git Connector with patch release string 2017.1/1572461
  • A working P4 Server server, either 17.1 patch 2017.1/1574018 or 17.2
  • A Perforce TeamHub repository that is not empty. This repository will be the source for mirroring into the P4 graph depot.
  • A Perforce TeamHub bot account you can use instead of personal credentials. The two options are:
    • A regular bot with access to relevant projects and repositories on the team view
    • A company admin bot account, which has access to every repository inside the company

For more information, see Bots & programmatic repository access in the Perforce TeamHub Documentation.

Installation of Perforce TeamHub On-Premise

You, the Git Connector administrator:

  1. Go to the Download Perforce TeamHub page.
  2. Locate the Perforce TeamHub package to download.
    See the installation instructions at Getting started with administration for Perforce TeamHub.
  3. Run the package for an on-premise installation of Perforce TeamHub.

Next steps

Configure for HTTP or SSH. Optionally, set up automated builds with Jenkins.

In this section: