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

P4 CLI Documentation | 2026.1

# Streams

Using a set of 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. has advantages over using a set traditional branches (noun) A set of related files that exist at a specific location in the P4 depot as a result of being copied to that location, as opposed to being added to that location. A group of related files is often referred to as a codeline. To associate code reviews in P4 Code Review (formerly Helix Swarm) with the projects they are part of, add the 'branch' paths in the P4 Code Reviewproject. (verb) To create a codeline by copying another codeline with the 'p4 integrate', 'p4 copy', or 'p4 populate' command.. As your organization develops and releases its products, change propagates across a stream hierarchy The set of parent-to-child relationships between streams in a stream depot. according to Flow rules that guide merge 1. To create new files from existing files, preserving their history when branching. 2. To propagate changes from one set of files to another. 3. The process of combining the contents of two conflicting file revisions into a single file, typically using a merge tool, such as P4 Merge. and copy actions to support stability and innovation.

A stream:

- Resides in a stream depot A depot used with streams and stream clients. A stream depot has structured branching, unlike the free-form branching of other depot types. See also 'classic depot' and 'graph depot'..
- Can be used to manage files in a way that resembles branches, but with additional functionality and structure.
- Is ideal for implementing the The mainline model, which includes multiple Stream types.
- Eliminates much of the administrative work needed to define branches, create workspaces, and manage merges.
- Enables the generation of stream view A dedicated view shared by all clients of the stream. A stream view is defined by the Paths, Remapped, and Ignored fields of the stream specification.A stream view can be seen with the 'p4 stream -ov' command. for associated workspaces, so you don't need to update views manually.

In this section:

Your search for returned results