mkactivity
Creates an activity
Applicability
Product |
Command type |
|---|---|
VersionVault |
cleartool subcommand |
|
VersionVault Remote Client |
rcleartool subcommand |
Platform |
|---|
UNIX® |
|
Linux® |
Windows® |
Synopsis
- VersionVault--Create an activity:
- mkact/ivity [ -c/omment comment | -cfi/le pname | -cq/uery
- | -cqe/ach | -nc/omment ] [ -hea/dline
headline ]
[ -in stream-selector ] [ -nse/t ] [ -f/orce ] [ activity-selector ...]
- VersionVault--Create an activity and associate
it with a task:
- mkact/ivity [ -tasks task-selector ...] [ activity-selector ...]
- VersionVault Remote Client--Create an
activity:
- mkact/ivity [ -c/omment comment | -cq/uery
- | -cqe/ach | -nc/omment ] [ -hea/dline
headline ]
[ -in stream-selector ] [ -nse/t ] [ -f/orce ] [ activity-selector ...]
Description
The mkactivity command creates an activity. Activities track the work you do in completing a development task. An activity consists of a headline, which describes the task, and a change set, which identifies all versions of elements that are created or modified by work on the activity.
Each stream can have one current activity, which records any changes being made. Use -nset if you do not want to use an activity immediately. To begin recording changes in an activity, issue a setactivity command from a view that is attached to the activity's stream.
Restrictions
Identities
No special identity required.
Locks
An error occurs if one or more of these objects are locked: the project VOB.
Mastership
(Replicated VOBs only) No mastership restrictions.
Options and arguments
Commenting
- For information on commenting options (-comment, -cfi/le, -cquery, -cqeach -ncomment), see comments.
Assigning a headline to an activity
- Default
- The activity's name as specified by the activity-selector argument.
- -hea/dline headline
- Specifies a description of the activity. The headline argument can be a character string of any length. Enclose a headline with special characters in double quotes. The headline is applied to all activities created with this invocation of the command.
Specifying the stream
- Default
- The stream attached to the current view.
- -in stream-selector
- Specifies that the activity be created in this stream.
stream-selector is of the form [stream:]stream-name[@vob-selector], where vob-selector specifies the stream's project VOB.
Setting the current activity
- Default
- If one activity is created with this command: the newly created activity. If more than one activity is created or any number of activities is created outside a view context: none.
- -nse/t
- Specifies that the new activity not be set as the current activity for the view.
Confirmation step
- Default
- Prompts for confirmation of a generated name for the activity if no name is specified by activity-selector.
- -f/orce
- Suppresses the confirmation step.
Specifying CMI tasks
- Default
- The tasks that are associated with the current view.
- -tasks task-selector ...
- Specifies the CMI-provided tasks that are to be associated with the activity. task-selector is of the form task@provider-name.
Naming the activity
- Default
- If one activity is created with this command: a generated name. If more than one activity is created: none.
- activity-selector ...
- Specifies one or more activities to create.
You can specify an activity as a simple name or as an object selector of the form [activity]:name@vob-selector, where vob-selector specifies a project VOB (see the cleartool reference page). If you specify a simple name and the current directory is not a project VOB, this command assumes that the activity resides in the project VOB associated with the stream attached to the current view. If the current directory is a project VOB, that project VOB is the context for identifying the activity.
The activity name must be unique within the PVOB. All UCM objects share the same namespace. You'll get an error if the name you provide collides with the name of an existing UCM object, for example, a stream.
Examples
The UNIX system and Linux examples in this section are written for use in csh. If you use another shell, you may need to use different quoting and escaping conventions.
The Windows examples that include wildcards or quoting are written for use in cleartool interactive mode. If you use cleartool single-command mode, you may need to change the wildcards and quoting to make your command interpreter process the command appropriately.
In cleartool single-command mode, cmd-context represents the UNIX system and Linux shells or Windows command interpreter prompt, followed by the cleartool command. In cleartool interactive mode, cmd-context represents the interactive cleartool prompt.
- Create an activity, but do not set it to be the current
activity for the view.
cmd-context mkact -nset
Create activity with automatically generated name? [yes] yes
Created activity "activity990917.133218". - Create an activity. The activity
is created in the stream attached to the current view.
cmd-context mkact new_activity
Created activity "new_activity".
Set activity "new_activity" in view "java_int". - Create an activity whose name
is generated automatically. You are not prompted for confirmation.
cmd-context mkact -f
Created activity "activity990917.134751".
Set activity "activity990917.134751" in view "java_int". - Create an activity with the headline "Create directories".
cmd-context mkactivity -headline "Create directories" create_directories
Created activity "create_directories".
Set activity "create_directories" in view "webo_integ". - Create an activity that is
associated with an RTC task.
cmd-context mkactivity -tasks task1@RTCPROV activity1