Helix4Git Administrator Guide (2019.2)

Architecture and components

Helix4Git consists of two components:

  • Helix server (or p4d), the traditional Helix Core server
    augmented for Git support
  • The Git Connector, which acts as a Git server to Git clients,
    such as Helix TeamHub, GitLab, and GitHub.

Git users use a Git client to pull files from the graph depot to make modifications and then push the changes back into the graph depot. The Git client communicates with the Helix server through the Git Connector.

In support of advanced workflows for blended assets, such as text and large binaries in build and test automation, you can also directly sync and view graph depot content through a command line client into a single classic Helix server workspace.

Note

To edit the graph depot files associated with a classic workspace, you must use a Git client.

A typical scenario:

  1. A Git user pushes changes to the Git Connector.
  2. The Git Connectorpushes the changes to the Helix server.
  3. A continuous integration (CI) server, such as P4Jenkins, detects changes and runs a build using one workspace that can include multiple Git repos and classic depot files.