02.05.2013 Views

Description - Mks.com

Description - Mks.com

Description - Mks.com

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

si snapshot<br />

records the state of a sandbox.<br />

SYNOPSIS<br />

si snapshot [--targetDevpath=value] [--author=value] [-d|--description=value]<br />

[--descriptionFile=snapshot] [-L|--label=value] [--[no]labelMembers]<br />

[--[no]notify] [-s|--state=value] [--[no]stateMembers] [-S|--sandbox=value]<br />

[--hostname=server] [--port=number] [--password=password] [--user=name]<br />

[(-?|--usage)] [(-N|--no)] [(-Y|--yes)] [--[no]batch] [--cwd=directory]<br />

[--forceConfirm=[yes|no]] [(-g|--gui)] [--quiet] [--settingsUI=[gui|default]]<br />

[--status=[none|gui|default]]<br />

DESCRIPTION<br />

si snapshot records a capture of the current state of a sandbox, where each element in the<br />

sandbox can be identified with a pre-existing entity in the repository on the Integrity Server. The<br />

sandbox snapshot creates a standard project revision from which a build sandbox can be created<br />

and a development path assigned. The project revision number takes the form of a branched<br />

revision in the project history. For example, if the head revision of the project is 1.1, then the<br />

project revision created by the snapshot will be 1.1.1.1.<br />

Note: si snapshot records the state of a sandbox, while si checkpoint records the state of a<br />

project. Checkpointing is re<strong>com</strong>mended for recording milestones during the development of a<br />

project; however, there may be situations where you may need to take a snapshot of a sandbox to<br />

record the state for later use.<br />

The state of a sandbox is defined by its set of elements, which include the following:<br />

● sandbox members identified with an archive and working revision from which the working<br />

file was created<br />

● former members that were dropped, but are still present in your sandbox<br />

● subsandboxes, identified by project name and type<br />

● former subsandboxes that were dropped but are still present in your sandbox<br />

Note the following about how si snapshot handles the set of sandbox elements:<br />

● To be included in the snapshot, all working files must be checked in. There must be no<br />

working file changes in the sandbox.<br />

● If the working file revision differs from the member revision, it is the working file revision that<br />

is included in the snapshot.<br />

● Members with no working files are not included in the snapshot.<br />

243 of 457

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!