User Guide - Mks.com

Chapter 5: Project and Sandbox Operations
Importing a
Sandbox
138
Variant creates a sandbox based upon a specific revision of the
master project and is used for branching off the main
development path. For more information on variant sandboxes,
see “Creating Variant Sandboxes and Development Paths” on
page 146.
NOTE
From the Development Path Name list, select a development path
name, for example, Aurora_Beta_Variant.
The Variant option is unavailable if there are no available development paths.
To create a development path, see “Creating a Development Path” on page 147.
Build creates a static sandbox based upon a specific revision of the
master project that is used for building or testing the project, but
not for further development. For more information on build
sandboxes, see “Using Build Sandboxes” on page 150.
To specify a revision to base the build project, do one of the
following:
Select Revision, and from the list select a project revision
number, for example, 1.1.
Select Label, and from the list select a project label.
9 To accept the options, click Finish.
The sandbox appears in a Sandbox view (see “Sandbox View” on
page 469).
To modify the options, click Back.
You can also create a sandbox from the Registered Sandboxes view.
With the Registered Sandboxes view open, click Create. Specify the
server name and port number in the Specify Server Connection dialog
box, and click OK. The Create Sandbox Wizard appears. To finish
creating your sandbox complete previous steps 2 through 9.
When you create a sandbox, it is automatically registered with the Integrity
Server; however, sandboxes created with earlier versions of
Source Integrity must be imported to register them with the Integrity
Server.
u s e r g u i d e