This subcommand shows the process rules for the specified process.
ccm process -s|-sh|-show (pr|prs|process_rule|process_rules) [-f|-format format] [-nf|-noformat] ([-ch|-column_header] | [-nch|-nocolumn_header]) [-sep|-separator separator] ([-sby|-sortby sortspec] | [-ns|-nosort|-no_sort]) [-gby|-groupby groupformat] [-u|-unnumbered] process_spec...
A keyword can be built-in (%fullname, %displayname, %objectname) or the name of any existing attribute such as %modify_time or %status.
See Built-In keywords for a list of keywords.
A process groups process rules into a named set that are designed to work together.
A process is used to specify the process rules that you can use for a release. These are the built-in processes, process rules, and purposes:
Process | Process Rule | Purpose |
---|---|---|
standard | Collaborative Development | Collaborative Development |
distributed | Custom Development | Custom Development |
You can create your own process to define a specific way for a team to work. For example, a build manager for a team working on a GUI project creates a process called GUI Process. This process contains a custom purpose called Beta Test with a corresponding process rule called Beta Test. The process rule defines a new level of testing for the beta release. The build manager uses the new Beta Test process rule to perform builds to prepare for the team beta test release, and the process rule can only be found in the new process, GUI Process.