cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

createsandbox - development path and project options are mutually exclusive with new project syntax

SOLVED
Highlighted
Level 4

createsandbox - development path and project options are mutually exclusive with new project syntax

Hello,

 

Creation of build sandbox with a checkpoint revision using the following syntax fails with a message stating that "development path and project options are mutually exclusive with new project syntax"

si createsandbox -P<project path> -projectRevision=1.43

 

Integrity Client version is 11

 

The command works fine without the projectRevision option.

 

What is the new syntax for specifying checkpoint version ?

 

Thanks,

Satish K

 

1 ACCEPTED SOLUTION

Accepted Solutions

Re: createsandbox - development path and project options are mutually exclusive with new project syn

Hi Satish,

What syntax did you use for the project path? The commands accept two different project formats:

Flat Path: /Test/project.pj

Config Path: #/Test   <-- begins with a # sign

 

Config Paths can already include variants and build numbers.

For example the config path syntax of:

si viewproject -P #/Test#d=MyDev

is equivalent to Flat path syntax:

si viewproject -P /Test/project.pj  --devPath=MyDev

Making the following an invalid command:

si viewproject -P #/Test#d=MyDev --projectRevision=1.1.1.1
*** The development path and build projects options are mutually exclusive with new project syntaxes. Specify one or the other,


In other words, using a configpath syntax in your -P parameter will throw the error if you also try to use --devPath or --projectRevision.

 

Hope this helps!

 

2 REPLIES 2

Re: createsandbox - development path and project options are mutually exclusive with new project syn

Hi Satish,

What syntax did you use for the project path? The commands accept two different project formats:

Flat Path: /Test/project.pj

Config Path: #/Test   <-- begins with a # sign

 

Config Paths can already include variants and build numbers.

For example the config path syntax of:

si viewproject -P #/Test#d=MyDev

is equivalent to Flat path syntax:

si viewproject -P /Test/project.pj  --devPath=MyDev

Making the following an invalid command:

si viewproject -P #/Test#d=MyDev --projectRevision=1.1.1.1
*** The development path and build projects options are mutually exclusive with new project syntaxes. Specify one or the other,


In other words, using a configpath syntax in your -P parameter will throw the error if you also try to use --devPath or --projectRevision.

 

Hope this helps!

 

Re: createsandbox - development path and project options are mutually exclusive with new project syn

Also, the syntax for giving a project revision (build) in the configuration path is #b=[rev] or #b=[label], where [rev] is the project revision and [label] is a label on the project revision.

 

e.g. #/MyProject#sub/sub2#b=1.34