Skip to main content
S
satishk1-Visitor
1-Visitor
December 25, 2018
Solved

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

  • December 25, 2018
  • 1 reply
  • 2593 views

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

 

Best answer by ascott

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!

 

1 reply

A
ascott17-PeridotAnswer
17-Peridot
December 27, 2018

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!

 

    A
    awalsh5-Regular Member
    5-Regular Member
    January 4, 2019

    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

      Terms & ConditionsAccessibility statement