Modifying a process rule

About this task

This subcommand modifies the specified process rules. You must be working as a Process rules manager to use this command.

ccm pr|process_rule|ut|update_temp|update_template|rt|recon_temp|
        reconfigure_template -m|-modify 
        [(-fol|-folder|-folders folder_spec)...] [(-ft|-folder_temp|
        -folder_temps|-folder_template|-folder_templates 
        folder_template_spec)...] [-bn|-baseline_name baseline_spec] 
        [-lb|-latest_baseline] [-usb|-user_selected_baseline] 
        [-lbp|-latest_baseline_projects] [-lsp|-latest_static_projects] 
        [-lsbmp|-latest_static_or_build_management_projects] 
        [-brp|-baseline_release_purpose|-baseline_release_purposes 
        release_purposes ( [-pr|-prepend] | [-ap|-append] )] 
        [-pb|-prep_baseline] [-nopb|-noprep_baseline] 
        [-matching version_matching_string] process_rule_spec...
-ap|-append
When used with the -brp|-baseline_release_purpose|-baseline_release_purposes option, specifies that the releases should be appended to the current release-purpose pair list.
-brp|-baseline_release_purpose|-baseline_release_purposes release_purposes
Specifies the baseline release and purpose pairs for the process rule. The baseline release purpose list is used when the process rule uses the latest baseline selection mode. The order of the list is important. In latest baseline search mode, update looks for baselines matching the first release and purpose. If none are found, it looks for baselines matching the second release and purpose.

The release_purposes value is a list of one of more items each of which is a release_spec, a colon (:), and a purpose name. You can set the release_spec to a single release, or be the keyword %release or %baseline_release. The %release keyword means the current release for that process rule. The %baseline_release keyword means the baseline release of the process rule's release. The purpose name must be a defined purpose.

If -ap|-append is specified, the specified release-purpose pairs are appending to the current list. If -pr|-prepend is specified, the specified release-purpose pairs are prepended to the current list. If neither option is specified, the specified release-purposes replace the current list.

-bn|-baseline_name baseline_spec
Specifies that the process rule uses the selection mode for the specified baseline. You can set baseline_spec to a single baseline.
-fol|-folder|-folders folder_spec
Specifies the folders to be removed from each process rule. Generic process rules may only have folder templates.
-ft|-folder_temp|-folder_temps|-folder_template|-folder_templates folder_template_spec
Specifies the folder templates to be removed from each process rule.
-lb|-latest_baseline
Specifies that the process rule should use the latest baseline. When a project grouping that uses this process rule is updated, the latest baseline is found that matches the specified baseline release-purpose pair list.
-lbp|-latest_baseline_projects
Specifies that the process rule should use the latest baseline project. When a project grouping uses this process rule and a project is updated, the latest project matching the version matching and prep baseline criteria is selected as the baseline project.
-lsp|-latest_static_projects
Specifies that the process rule should use the latest static projects. This option cannot be used with the -pb|-prep_baseline option.
-lsbmp|-latest_static_or_build_management_projects
Specifies that the process rule should should use the latest static or build management projects. This option cannot be used with the -nopb|-noprep_baseline option.
-matching version_matching_string
When the process rule uses a selection mode of latest baseline projects, this specifies any additional criteria to match against the versions of candidate baseline projects.

You can enter a version that can be used to identify the baseline. Use this field if specifying the release of the baseline is insufficient because you have more than one release version of a project with the same release value.

For example, if a company has three released project hierarchies, all for release 1.0: the project versions are 1.0_alpha, 1.0_beta, and 1.0_gr. In this case, specifying the Baseline Release option as 1.0 is not enough to identify projects that use this process rule. You would set the Baseline Versions Matching option to 1.0_gr to indicate that the project with a version of 1.0_gr should be used as the baseline.

If all baselines in the 1.0_gr project hierarchy do not have identical versions, but their versions are similar, you can specify a wildcard. For example, if your project hierarchy contains projects with versions 1.0_gr, 1.0_gr_unix, and 1.0_gr_windows, you could set the Baseline Versions Matching option to 1.0_gr*. This setting would select the version with the prefix 1.0_gr, even though the remainder of the version might differ. (If a project has more than one choice for a baseline, it will select the baseline whose platform matches. For example, project 2.0_int_unix might identify 1.0_gr_unix and 1.0_gr_windows as potential baselines, but it will check for a matching platform, then use 1.0_gr_unix. This is because Rational Synergy is set up to support development of parallel platforms by default.)

-modify
Specifies to modify the properties of an existing process rule. This subcommand accepts one or more Process rule specification arguments. You can set each to multiple objects. It accepts the -bn|-baseline_name option, which accepts a Baseline specification that you can set to a single baseline object. The results of this option do not update the query selection set.
-nopb|-noprep_baseline
Valid only when the process rule has a baseline selection mode of latest_baseline_projects. It indicates that prep state projects are not to be considered as potential baseline projects for individual projects that use this process rule. Use the -lsp|-latest_static_projects option instead.
-pb|-prep_baseline
Valid only when the process rule has a baseline selection mode of latest_baseline_projects. It indicates that prep state projects should be considered as potential baseline projects for individual projects that use this process rule. Use the -lsbmp|-latest_static_or_build_management_projects option instead.
process_rule_spec
Specifies the process rules to modify. See Process rule specification for details.
pr|-prepend
When used with the -brp|-baseline_release_purpose|-baseline_release_purposes option, the specified release-purpose pairs are prepended to the current list.
-usb|-user_selected_baseline
Specifies that the process rule does not specify a baseline that is to be used to find baseline projects. The baseline is selected by the user.

Examples

About this task

  • Set the 2.1:Insulated Development process rule to use the latest baseline.

    ccm pr -m "2.1:Insulated Development" -latest_baseline

  • Set the 2.1:Insulated Development process rule to use the latest baseline projects with the specified release and purpose combinations.

    ccm pr -m "2.1:Insulated Development" -latest_baseline_projects -baseline_release_purpose "2.1:Integration Testing,2.1:System Testing,2.0:Any"

  • Modify the list of release/purpose pairs that are used by a specific process rule to search for a baseline.

    ccm pr -modify -baseline_release_purposes "2.0:Any,1.0:System Testing" -prepend "2.0:Integration Testing"

  • Select a baseline named Build_1234_int for a process rule whose process_rule_spec is 2.0:Insulated Development.

    ccm process_rule -modify -bn Build_1234_int "2.0:Insulated Development"


Feedback