- chproj·ect [ –c·omment comment | –cfi·le pname | –cq·uery
- | –cqe·ach | –nc·omment ]
[ –amo·dcomp component-selector[,...] ]
[ –dmo·dcomp component-selector[,...] ]
[ –to to-folder-selector ] [ –reb·ase_level promotion-level ]
[ –pol·icy policy-keyword[,...] ] [ –npo·licy policy-keyword[,...] ]
[ –spo·licy policy-keyword[,...] ]
[ –crm·enable ClearQuest-user-database-name | –ncr·menable ]
[ –bln·ame_template baseline-naming-template ]
The chproject command modifies one or more UCM projects in the following ways:
- Adds one or more modifiable components to a project
- Removes one or more components from the project's modifiable component list
- Moves a project to another folder
- Changes the promotion level required of a baseline before it can be recommended by a stream in the project
- Sets policy for a project
- Enables or disables a project for use with Rational ClearQuest
- Defines the baseline name template
For information about changing the project's name, see rename.
Adding Modifiable Components
Over time, a project's scope can expand, and you may need to add modifiable components to the project. The –amodcomp option allows you to add one or more modifiable components. For the streams in the project to capture the changes in component modifiability, do one of two things:
- If the components have a baseline in the stream, synchronize the stream to the project first with chstream –generate, then reconfigure the views attached to the stream with setcs –stream. For the project's integration stream, however, you need only reconfigure the integration views.
- If the components don't yet have a baseline in the stream, add baselines for these components with rebase –baseline.
Converting Components from Modifiable to Read-Only
If you made some components modifiable when you set up a project and later change your mind, the –dmodcomp option allows you to remove one or more components from the project's modifiable component list. A component cannot be removed from the list if any changes have been made to it in the project. Before performing this operation, verify that no development stream has changes to the component. A warning is issued if any of the following is true:
- The component or VOB is replicated. Any modification in development streams of replicated VOBs cannot be delivered.
- One or more of the project's streams are unavailable.
- The component is already unmodifiable.
After you convert the components to read-only, regenerate the views as needed with setcs –stream.
Setting Required Promotion Levels for Recommended Baselines
When setting recommended baselines, you can either specify a list of baselines that satisfy certain requirements, or let UCM compute the set of baselines that meet the rebase level specification. A project's rebase level is the minimum promotion level a baseline must have in order to be recommended by a stream in the project if you choose to use rebase levels to set the recommended baselines. For example, if Project A has three promotion levels — REJECTED, TESTED, and RELEASED (in ascending order) — and TESTED is the rebase level, the latest baselines labeled TESTED or RELEASED can be recommended by a stream with chstream –recommended –default. See chstream, rebase and setplevel for more information.
Using Rational ClearQuest with UCM Projects
You can link or unlink a UCM project to a ClearQuest database with the –crmenable or –ncrmenable options. When you enable ClearQuest for a UCM project that contains UCM activities, then for each UCM activity, a ClearQuest record of type UCMUtilityActivity is created and linked to the activity. This process is called activity migration. If you disable a link to ClearQuest from a UCM project that contains activities, all its activities are unlinked from their ClearQuest records.
The –crmenable and –ncrmenable options display a summary of the number of activities that have been migrated or unlinked.
In MultiSite, you are informed when activities cannot be migrated or linked because they are not mastered in the current UCM project VOB replica. These activities are listed along with a list of replicas from which to run the command again to correct the problem.
You can also use the –crmenable and –ncrmenable options to check for possible linking errors. If you believe that your project enabled for ClearQuest may contain activities that are not linked to a ClearQuest record, run chproject –crmenable. This operation scans all activities in the project, migrating all activities that are not linked. To check for linked activities in projects that have been disabled for use with ClearQuest, run chproject –ncrmenable. This operation removes links between activities as needed. For more information, see Managing Software Projects.
You must have one of the following identities:
- Project owner
- Project VOB owner
- root (UNIX)
- Member of the ClearCase administrators group (ClearCase on Windows only)
- Local administrator of the ClearCase LT server host (ClearCase LT on Windows only)
Setting the project policy POLICY_CHPROJECT_UNRESTRICTED skips the permission checking. For more information, see the mkproject reference page.
An error occurs if there are locks on any of the following objects: the project, the UCM project VOB.
OPTIONS AND ARGUMENTS
Event Records and Comments
- Creates one or more event records,
with commenting controlled by your .clearcase_profile file
(default: –cq). See the comments reference page. Comments can be edited with chevent.
- –c·omment comment | –cfi·le comment-file-pname |–cq·uery | –cqe·ach | –nc·omment
- Overrides the default with the option you specify. See the comments reference
Adding to the List of Modifiable Components for a Project
Removing from the List of Modifiable Components for a Project
Moving the Project to Another Folder
Changing the Recommended Promotion Level for a Rebase Operation
- –reb·ase_level promotion-level
- Changes the promotion level required for
baselines to be recommended by a stream in the project. When you run chstream –recommended –default to set recommended baselines, the latest baseline for each component in
the integration stream at or above this promotion level is recommended.
Setting Project Policy
- –pol·icy policy-keyword
- Enables the specified policy. For information
about project policies, see mkproject.
- –npo·licy policy-keyword
- Disables the specified policy. For information
about project policies, see mkproject.
- –spo·licy policy-keyword
- Allows the specified policy to be enabled
or disabled by individual streams. For information about project policies,
Linking a Project to Rational ClearQuest
- No linking.
- –crm·enable ClearQuest-user-database-name
- Enables a link from the project to the specified Rational ClearQuest
database. The schema of the ClearQuest database must be enabled for UCM, and
your system must be configured for the correct schema repository.
- Disables use of Rational ClearQuest for
the specified project.
Modifying the Baseline Name Template
- Baseline identifiers are made up of two parts: a user-specifiable root
name and a generated, unique numeric extension.
- –bln·ame_template baseline-naming-template
- Defines the baseline name template for a project if a template has not
been defined, or replaces the template if one already exists. baseline-naming-template specifies
the tokens to be used in the baseline name and it can include any of the following
tokens separated by commas:
basename project stream component date time user host
When you create baselines, UCM replaces commas with underscores in the baseline name.
The UNIX 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 shell or Windows command interpreter prompt, followed by the cleartool command. In cleartool interactive mode, cmd-context represents the interactive cleartool prompt.
Note: In the UNIX examples that follow, arguments and output that show multicomponent VOB tags are not applicable to ClearCase LT, which recognizes only single-component VOB tags. In this manual, a multicomponent VOB tag is by convention a two-component VOB tag of the form /vobs/vob-tag-leaf—for example, /vobs/src. A single-component VOB tag consists of a leaf only—for example, /src. In all other respects, the examples are valid for ClearCase LT.
the modifiable component, webo_modeler, to the project.
cmd-context chproject -amod webo_modeler webo_proj1@/vobs/webo_pvob
Changed modifiable component list for project "webo_proj1@/vobs/webo_pvob".
Propagating changes to the integration stream "IntStream1".
Changes to modifiability of components must be propagated to streams and
their views. Use `cleartool chstream -generate' to update the stream with
``cleartool setcs -stream' for each view attached to the stream or see the
stream and view properties pages.
Changed modifiable component list and propagated changes to streams in
- Define the baseline name template for the CQ_ASP_V6.0 project.