Description - Mks.com

si createsandbox
creates a new sandbox on your local machine
SYNOPSIS
si createsandbox [(-R|--[no|confirm]recurse)] [--lineTerminator=[lf|crlf|native]]
[--[no]populate] [--[no]sparse] [--[no]openView] [--[no]shared]
[(-Pproject|--project=project)] [--devpath=path] [--projectRevision=rev]
[--hostname=server] [--port=number] [--password=password] [--user=name]
[(-?|--usage)] [(-F file|--selectionFile=file)] [(-N|--no)] [(-Y|--yes)] [--[no]batch]
[--cwd=directory] [--forceConfirm=[yes|no]] [(-g|--gui)] [--quiet]
[--settingsUI=[gui|default]] [--status=[none|gui|default]] [--xmlapi] directory
DESCRIPTION
si createsandbox creates a new sandbox on the client machine in a specified directory. When
creating a sandbox you are able to determine the type of sandbox you want it to be:
● The default regular type creates a sandbox based upon the current state of the project.
● Choosing to create a variant creates a sandbox based upon a specific revision of the
master project and is used for branching off the main development path. You first have to
specify a development path other than the default one; to create a development path, see
the si createdevpath command.
● You may also choose to create a build sandbox. A build sandbox 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.
Variant Sandboxes and Development Paths
By default, si createsandbox creates regular sandboxes that are based upon the current state
of the project. You can also create a variant sandbox, a sandbox that is based upon a previously
checkpointed revision of the project. When you create a variant sandbox, you choose a checkpoint
(snapshot) of your project and use it as a starting point for new development. MKS Source Integrity
allows you to do this by defining a new development path and then specifying that path with the
--devpath option. For example:
si createsandbox --devpath=MyVariant
A development path is an identifier given to a new direction of software development. Changes
made through the development path are kept separate from the main development trunk unless
you choose to merge them (see si merge) into it later. Source Integrity allows multiple
developers to point to the same development path, each using their own variant sandbox. In the
86 of 457