Helix Core is now P4. Product user interfaces will be updated soon. Learn more >>

P4 CLI Documentation | 2026.1

# Parts of P4

Perforce P4 is an enterprise version control management system that run in a client server environment. A client application, such as the command line client, P4 CLI, connects to the P4 Server (P4D).

| P4 client applications allow you to check files out of the depot, resolve conflicts, and make your local changes available to other users by submitting your changelist The changes to files or stream specifications along with metadata, such as the list of changed files, their version numbers, the submitter of the changelist, and the submitter's description of the changes. A changelist is the unit of versioned work. to the depot. To get the latest version of files, you sync from a shared repository called the depot A file repository hosted on the P4 Server. A depot is the top-level unit of storage for versioned files, which are also known as depot files, archive files, or source files. It contains all versions of all files ever submitted to the depot. Except for obliterated files, any version of any file can be restored, including deleted files, but not obliterated files. An installation can have multiple depots, and they might be of different types, such as a local depot and a stream depot., which contains every revision of every archive file Versioned files that users submitted to a depot. under version management. You edit files on your computer in your client workspace Directories on your machine where you work on file revisions that are managed by P4 Server.. Integrations are available, such as Microsoft Visual Studio, Eclipse, Jenkins, MATLAB\Simulink, and ElasticSearch (P4Search for P4 DAM and P4 Code Review). APIs enable developers to create custom client applications. The P4 Server database tracks the status of users, groups, files, and streams An enhanced type of branch with a dedicated view for clients of the stream (see 'stream view') and built-in rules that determine how changes flow across the stream depot (see 'stream hierarchy'). A stream specification defines a stream. In P4V, stream specs are visible in the Streams Graph and the Streams tab..

Customisation of the P4 Server can be achieved in various ways, including the setting of user permissions, setting Environment and registry variables and Configurables, as well as enhancing behavior by creating Triggers and extensions.

The Git Connector can mirror Git repos within a P4 Server 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..

P4 Server also supports a decentralized workflow. To learn more, see Distributed versioning (DVCS) in the P4 Server Administration Documentation.

Your search for returned results