User Guide - MKS

Controlling Projects
Restoring a project is useful when development must revert back to an
earlier version and there are no plans to proceed from the current version
of the project. Restoring a project is not an option when the goal is to test a
particular version.
IMPORTANT
Do not use the Restore Project command to create a new development branch
from a previously checkpointed project revision. For new development paths,
you should instead create a development path (see “Creating Variant
Sandboxes and Development Paths” on page 139).
Source Integrity performs the Restore Project command as follows:
A checkpoint is performed on the current project revision.
The project is restored to the target revision.
A final checkpoint of the restored revision is made.
Therefore, for each project you restore, two revisions are generated. For
example, if the head revision of the project is 1.4 and you decide to restore
it to Revision 1.2, the following project revisions are generated:
1.6 final checkpoint
1.5 pre-checkpoint
You would then continue your project development work from revision
1.6.
You can effectively undo the Restore Project command by restoring the
project to the pre-checkpointed revision. Build projects cannot be restored
using the Restore Project command.
You can restore any registered project or subproject through the graphical
user interface, using either a Project or Sandbox window, or through the
command line interface. When you work through a sandbox or
subsandbox, the corresponding master project is referenced. The Restore
Project command can be applied to both normal and variant projects.
To restore a project or subproject in the graphical user interface
1 With a Project or Sandbox window open, select the project or sandbox.
2 From a Project window, select Project > Restore Project.
From a Sandbox window, select Sandbox > Restore Project.
The Restore Project dialog box appears.
241