Define a workspace and bind it to the stream
Before you can work in a stream, you must define a workspace associated with the stream. When you associate a workspace with a stream, Helix Core Server generates the workspace view based on the structure of the stream. Stream users never need edit the workspace view (and cannot manually alter it). If the structure of the stream changes, Helix Core Server updates the views of workspaces associated with the stream on an as-needed basis.
Users of a non-stream classic depot A repository of Helix Core files that is not streams-based. Uses the Perforce file revision model, not the graph model. The default depot name is depot. See also default depot, stream depot, and graph depot. define a workspace by issuing the p4 client
command without passing the -S
option, and edit the
workspace view manually by editing the View
field in the
client spec. See
Configure workspace views.
Your
Helix Core Server
administrator might have already configured a client workspace for your
computer. If so, the Client
field in the client spec
displays the Client workspace name when the user issues the p4 client command.
If not, to create a workspace for a stream:
-
Issue the
p4 client
command, using the-S
option to specify the name of the associated stream.For example:
$ p4 client -S //JamCode/main
The workspace specification form is displayed.
- Configure the workspace Root directory and any other desired settings, and save the specification. For details, see Define a client workspace.
-
Verify that your workspace has been created by using
p4 clients
.For example:
$ p4 clients -S //JamCode/main
The next step is Populate the mainline stream.