Open topic with navigation

Creating new streams

To create a stream:

1. Choose File > New > Stream​ or right-click a stream in the Stream Graph and select Create New Stream from '<stream name>'…​.

   Note

   Streams must be created in a Streams depot. You cannot create a stream in a classic depot.

2. In the Stream dialog, specify the name of the stream.

   By default, the name you specify is used as the name of the folder (under the stream depot folder) in the depot where files in the stream are stored. To override the default folder name, go to the Advanced tab.

3. Choose the stream type.
4. (Optional) If you require a flow of change that is different from the default for the stream type, enable or disable the corresponding Change propagation option (To parent and From parent).

5. For release and development streams, choose the parent stream; for mainline streams, enter the depot where the mainline will be stored.

   By default, the stream inherits its parent’s stream view. To edit the view of the child stream, go to the Advanced tab.

   The Advanced tab options enable you to do the following:

   • Edit the inherited view.
   • Change the default locations of files mapped from the depot.
   • Lock the stream settings so that only the owner can edit them.
   • Restrict check-ins to the stream owner.

   • Allow to merge the stream’s content both up and down.

   • Specify file or folder patterns that you want ignored by the stream.

     Ignoring a file or folder pattern prevents users from submitting files or folders that follow that pattern, no matter the stream view definition. You can use the Ignored field to ensure that generated files are never checked in, for example. You can enter filenames, filename extensions, or file paths. Separate each with a line break. For example:

     /tmp # ignores files named "tmp"
     /tmp/... # ignores directories named tmp
     .tmp # itnores file names ending in .tmp
     

     Note

     Stream specifications do not allow wildcards (*), positional specifiers (%%1), or overlay mapping (+).

   Mainline, development, and release streams are only visible in the depot tree pane if the stream is populated.

6. (Optional) Select whether to Create a workspace for use with this stream..

   If you choose not to create a workspace immediately, you can do so later, when you want to work in the stream.

7. (Optional) Select whether to Branch files from parent on stream creation.

   If you choose not to branch files immediately, you can do so later using the Copy operation.

8. To save your entries, click OK.

Creating stream workspaces

To work in a stream, you must have a workspace for it. Helix Server generates the viewA description of the relationship between two sets of files. See workspace view, label view, branch view. (mapping of depot locations to client locations) for any stream workspace, but you must initiate the creation of the workspace. You can do so in the following ways:

• When you create a new stream using the Stream dialog, select the Create a workspace for use with this stream option.

• The first time that you select a stream to work in, you’ll be prompted to create a new workspace.

  See Selecting streams.

The Workspace dialog opens, with all necessary fields pre-populated to work with the current stream.

You can update any of the fields in the Workspace dialog, except Stream name and Workspace mappings (which can only be changed by updating the stream’s path configuration). If you want a "back-in-time" view of your stream, you can use the Stream At Change option to sync the stream using the stream’s view as of a specific changelist. When you use the Stream At Change option, you cannot submit changes to the files in the stream, since your workspace files are not at the head revision.