Parts of Helix Core Server

Helix Core Server (P4D) is an enterprise version management system. To get the latest version of files, you sync from a shared repository called the depotClosed A file repository hosted on the Helix Core 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 fileClosed Versioned files that users have submitted to a depot. under version management. You edit files on your computer in your client workspaceClosed Directories on your machine where you work on file revisions that are managed by Helix Core Server. By default, this name is set to the name of the machine on which your client workspace is located, but it can be overridden. Client workspaces, labels, and branch specifications cannot share the same name.).

The Helix Core 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 changelistClosed The changes to files or stream specifications along with metadata, such as the list of changed files, their version numbers, who submitted the changelist to the depot, and the submitter's description of the changes. A changelist is the unit of versioned work. See also atomic change transaction and changelist number. to the depot.

Many plugins and integrations are available, such as Microsoft Visual Studio, Eclipse, Jenkins, MATLAB\Simulink, and ElasticSearch (P4Search for Helix DAM and Helix Swarm).

The APIs enable developers to create custom client applications.

The p4d database tracks the status of users, groups, files, and streamsClosed A branch with built-in rules that determine which changes to propagate to files in a stream depot, and in what order. A stream specification defines a stream. A user creates a stream spec by using the 'p4 stream' command or in P4V with File > New Stream. In P4V, stream specs are visible in the Streams Graph and the Streams tab.. The administrator can work with logs, permissions, and configuration settings, as well as customize behavior with triggers and Helix Core Server Extensions. The Git Connector can mirror Git repos within a graph depotClosed A depot of type graph that is used to store Git repos managed by Helix Core Server. See also Git Connector and classic depot..

Helix Core Server also supports a decentralized (“distributed”) workflow. To learn more, see Using Helix Core Server for Distributed Versioning (DVCS).