02.05.2013 Views

User Guide - MKS

User Guide - MKS

User Guide - MKS

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Chapter 3: Getting Started Using Source Integrity<br />

Command Options<br />

50<br />

Add Subproject Select one of the following options as the preferred type of subproject when adding a<br />

subproject to a project:<br />

Normal adds a subproject based on the current state of the project.<br />

Variant adds a subproject based upon a specific revision of the master project and<br />

is used for branching off the main development path.<br />

Build adds a static subproject based upon a specific revision of the master project<br />

that is used for building or testing the project, but not for further development.<br />

Default adds a subproject based on the parent project type. For more information on<br />

the default type, see your administrator.<br />

Append Revision<br />

Description<br />

Recurse Into Subprojects appends the revision description recursively to subproject<br />

members.<br />

Apply Change Package Use Master causes Source Integrity to operate on the top-level sandbox. When the<br />

selected change package is associated with a member in a subsandbox, specifying<br />

Use Master causes the command to operate on the top-level sandbox for that<br />

subsandbox.<br />

Confirm Actions causes Source Integrity to confirm all operations with you before<br />

starting them.<br />

Verbose provides additional information to track the current state of the command.<br />

Other Project is Error terminates the command if the member being applied is in<br />

another project. If this setting is negated (as in noOtherProjectIsError), the<br />

information is displayed as a warning.<br />

Span Projects applies the command to any member in the specified in the change<br />

package, even if this involves a different project than you are starting from. Warning:<br />

This is the only operation that has the potential to affect other projects.<br />

Ignore Cross-Branch Entries causes Source Integrity to use the most recent revision<br />

when it encounters two revisions of the same member on two development paths.<br />

Already in Project is Error terminates the command if the member being applied is<br />

already in the project. If this setting is negated (as in<br />

noAlreadyInProjectIsError), the information is displayed as a warning.<br />

Ignore Server in Change Package causes Source Integrity to perform the Apply CP<br />

operation even if the change package members reside on different servers.<br />

Create Variants causes Source Integrity to create variant projects within the new<br />

project as required to apply the change package members. This option does not affect<br />

the Apply CP command.<br />

u s e r g u i d e

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

Saved successfully!

Ooh no, something went wrong!