P4V User Guide (2020.1)

Working with graph depots

P4V version 2020.1 is the first version to support workspaces of map to:

The following image shows an example of how P4V displays a graph depot that contains a repo that contains folders and files. Each repo indicates its current branch in parentheses, such as (master). Each file is identified with a SHA-1 hash that displays in the short form of 8 hexidecimal digits:

The P4V administrator can create a graph depot and assign access permissions to graph depots or repos . See P4Admin User Guide.

If your P4V administrator has granted you access, you can right-click a repo, and click Sync Repo To... The Sync Repo dialog appears, and you can sync to Latest, a Branch, a Tag, or a Commit SHA-1.

Important

In P4V version 2020.1,

  • a graph depot is read-only
  • if a hybrid workspace is of type writeable, the graph depot files are read-only
  • if a hybrid workspace is of type graph, all the files in the workspace are read-only

Repo folder information

If you sync a repo to a tag or a SHA-1, the repo folder shows [email protected] or [email protected]:

and the tooltip indicates @HEAD corresponds to the SHA-1 for both HaveCommit and HeadCommit.

Note

For details about repo file information in Helix Core server, see the output of p4 help-graph fstat

Tag names, if any, appear in the repo tooltip.

A branch can be [email protected] or Head [email protected]

Note

If you sync to a tag or a SHA-1 that is not an ancestor of your current branch, (HEAD [email protected]a1b2c3d4) appears to indicated that the repo is not sync'd to the latest state (HEAD) of any branch. For example,


Repo file information

A repo file is displayed like this:

filename.txt #haveBlob/headBlob

where a file is represented as a binary large object (blob):

Repo Client
headBlob represents the SHA-1 for the file content at the head revision haveBlob represents the SHA-1 for the file content at the have revision on the client
headCommit represents the commit SHA-1 for the file at the head revision haveCommit represents the commit SHA-1 for the file at the have revision on the client

In the depot tree tab, if file shows #none/headBlob, it means the file exists in the depot but it's not currently synced based on current tag or SHA-1.

means that the repo file is both at headBlob and at headCommit, such that

  • haveBlob matches headBlob and
  • haveCommit matches headCommit:

 

means that the repo file is at headBlob but not at headCommit, such that

  • haveBlob matches headBlob but
  • haveCommit does not match headCommit

In this case, just as with a classic file, you must sync to get latest before submitting.

p4v file notsync means that the repo file is not at headBlob and not at headCommit, such that

  • haveBlob does not match theheadBlob and
  • haveCommit does not matche headCommit