ACTIVATE
Syntax |
activate <-b buildSpace> [-s compartment] <-m activationMode> [-u user] [-a activityIDs] [-y] [--ignoreintersection] [--ignorebuilderrors] |
Arguments |
|
<-b buildSpace> |
The build space concerned in CBS. |
[-s compartment] |
If this option is not specified, all compartments of the build space are taken by default. |
<-m activation mode> |
This argument can take the following values: ● force – force means that predecessor activities are added to the request. ● reject – reject means that predecessor activities have to be activated first, otherwise the activation request will be rejected. |
[-u user] |
User whose pending activities should be activated. If this option is not specified, activities of all users are considered. |
[-a activityIDs] |
A comma-separated list of activity IDs to activate. Enclose the list of IDs into double quotes, for example: -a "id1,id2,id3". If this option is not specified, all pending activities are considered. If option -a is omitted you have to confirm this explicitly with option –y. Otherwise the application asks for a confirmation. |
[-y] |
Confirms that option -a has been omitted. |
[--ignoreintersection] |
Intersections on different files of the same DC should not be considered. As a consequence, only intersections on the same file are considered. |
[--ignorebuilderrors] |
The activation will be done despite build errors. |
Description |
Activates the specified activities. |