Architecture of Git Connector component

The P4 Git Connector component can be configured to “mirror” Git content into a graph depot A depot of type graph that is used to store Git repos managed by P4 Server. See also Git Connector and classic depot. within P4 Server.

The Git Connector acts as a Git server to Git clients, such as Perforce TeamHub, GitLab, and GitHub.

Git users can 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 P4 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 P4 Server workspace.

To edit the graph depot files associated with a classic workspace, you must use a Git client.
See also Working with graph depots in the P4 Visual Client (P4V) Documentation.

A typical scenario:

A Git user pushes changes to the Git Connector.
The Git Connector pushes the changes to the P4 Server.
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.