Showing process rule information

About this task

This subcommand shows information about the specified process rules. Any user may use this command.

ccm pr|process_rule|ut|update_temp|update_template|rt|recon_temp|
        reconfigure_template -s|-sh|-show (i|info|information) 
        -f|-format format [-nf|-noformat] 
        ([-ch|-column_header] | [-nch|-nocolumn_header]) 
        [-sep|-separator separator] process_rule_spec...
ccm pr|process_rule|ut|update_temp|update_template|rt|recon_temp|
        reconfigure_template -s|-sh|-show (i|info|information) 
        process_rule_spec...
options

-ch|-column_header

-f|-format format

-gby|-groupby groupformat

-nch|-nocolumn_header

-ns|-nosort|-no_sort

-sby|-sortby sortspec

-sep|-separator separator

-u|-unnumbered

Example

About this task

  • Show properties of the 2.1:Insulated Development process rule.
    ccm process_rule -show info "2.1:Insulated Development"

Description and uses

About this task

The process_rule command displays and sets process rules. Note that the process_rule command was referred to as the update_template and reconfigure_template commands in prior releases.

A process rule specifies how a baseline is chosen for a project grouping's update properties and for a project's update properties. Process rules support these selection modes:

  • Latest baseline

    The latest baseline matching the process rule's baseline release-purpose pair list is chosen as the baseline for the project grouping. For a project, the corresponding project in that baseline is used as the baseline project.

  • Specific baseline

    The baseline specified for the process rule is used for the project grouping. For a project, the corresponding project in that baseline is used as the baseline project.

  • User selected baseline

    A process rule does not specify a baseline. You must select a baseline for the project grouping's update properties manually. For a project, the corresponding project in that baseline is used as the baseline project.

  • Latest baseline projects

    A baseline project is chosen by getting the latest baseline projects that match the release or baseline release, and that match any specified version matching criteria on the project version.

A process rule specifies how a project is updated when an update operation is performed on the project. The combination of a project purpose and release value determines which process rule can be used in the project. Multiple process rules can be created for a release/purpose pair. You can set up rules, and then select rules to apply to a given release and purpose, and switch among the set of process rules during the course of a release. You can also reuse process rules for future releases, rather than continually modifying the process rule for each purpose.

Process rules are automatically created whenever one of the following occurs.

  • When a builder manager creates a new release with a specified process, a release-specific process rule is created for each generic process rule. If the build manager creates a release with generic process rules, a release specific process rule is created for each generic process rule.
  • When a build manager adds a new purpose to the list of valid purposes for a particular release value, a process rule is created for that unique combination of project purpose and release value.
  • When a build manager adds a generic process rule to a release, a release specific process rule is created from it.
  • When a build manager creates a new purpose, a general process rule is created for that purpose. The build manager must then edit this new (empty) process rule.
  • When a build manager copies a process rule.
  • When a build manager copies a generic process rule using a new generic process rule name.

General process rules are shipped with the product for both standard and distributed processes. A non-DCM-initialized database contains the standard process, and a DCM-initialized database contains both the standard and the distributed processes. The process rules have the same behavior in each, with these exceptions:

  • In the standard process, Collaborative Development collects all completed tasks from all databases, while in the distributed process, Local Collaborative Development collects all completed tasks from the local database.
  • In the standard process, Integration Testing collects all completed tasks from all databases, while in the distributed process, Local Integration Testing collects all completed tasks from the local database, and master integration tested tasks from foreign databases.

The standard process is used to provide process rules in the CLI when a purpose is specified.

You can specify which process rules to use when you create a new release. For more information, see the release command.


Feedback