Creates or previews the creation of a baseline. Build managers or users in the ccm_admin role can create baselines from one or more projects, baselines, or project groupings.
ccm baseline -c|-create [(-p|-project project_spec)...] [(-bl|-baseline baseline_spec)...] [(-pg|-project_grouping project_grouping_spec)...] [-rehearse] [-r|-release release_spec] [-purpose purpose] [-d|-desc|-description description] [-vt|-version_template version_template] [-b|-build build] [-s|-state state] ([-subprojects] | [-all_subprojects] | [-no_subprojects]) [baseline_name]
Note that the use of –subprojects, -no_subprojects, and –all_subprojects affect which subprojects are also added.
By default, if you use –baseline but not –project, subprojects are not included. However, if you use both –project and –baseline, then the –subprojects default implied by –project overrides the –no_subprojects default implied by –baseline.
If you do not specify a baseline_name, a unique name is automatically assigned to the baseline. This default name is in the form yyyymmdd. If needed, the default name is followed by an underscore and an incremental number to make it unique. For example, the first baseline created on April 1, 2002 has a default name of 20020401. The second such baseline created on the same day has a default name of 20020401_1.
If neither -project_grouping nor -baseline is specified, the default is
-subprojects. If either -project_grouping or -baseline is specified, the default is -no_sub_projects.
Note that –subprojects, -no_subprojects, and –all_subprojects affect which subprojects are added along with the project groupings.
A purpose is a setting that specifies the use of a project (e.g., Insulated Development, Integration Testing, System Testing).
Note that if you specify -purpose, you must also specify -release release_spec.
If any version conflicts are found, you will see a warning that lists all the product and project versions that are in conflict. The conflicts exist because the resulting version already exists in a new baseline or because the resulting version would not be a legal version string.
Note that if you specify -release, you must also specify -purpose purpose.
Creating a baseline in the released state is equivalent to creating one in the published_baseline state, and then releasing it.
This option applies to projects added with the -project, -project_grouping and
-baseline options. This is the default behavior if neither -project_grouping nor
-baseline is specified. If either -project_grouping or -baseline is specified, the default is -no_subprojects.
A version_template is any string, with optional keywords, with the form %keyword or %{keyword}. The keyword can be any Rational Synergy attribute or built-in keyword.
When an attribute is expanded, the corresponding attribute value from the build management project or product being examined is used. If an attribute or built-in keyword is not found for a specified keyword name, the empty string replaces the keyword.
If the instantiated version_template for any project or product in the baseline contains characters that are not allowed in a version string, those characters are replaced with the default version string replacement character. This is specified in the ccm.ini file, with the baseline_template_repl_char option. This default character is an underscore (_). For example, if %platform is part of a version template, and the build management project has a platform of SPARC-solaris, then the version string contains the string SPARC_solaris. Or, if %release is part of a product version template, and the prep product has a release of CM/6.5, then the version string contains the string CM_6.5.
If the instantiated version_template for any project or product in the baseline is already in use for another version of that project or product, the version is made unique by appending an underscore (_) and the first integer that will make the version unique, starting with 1. If this causes the version string to be too long, then a version based on the current date is used for that project or product, and a warning is given.
If you don’t specify –version_template, the default template is used. For more information, see sc_t_h_show_baseline_info.html#wp959846__wp962241.
The work area is updated if the work area template for the project includes the version. If a work area cannot be updated because it is not visible, and -skip_nonvisible_projects is not used, the operation continues and all errors are reported. If the work area is visible, but cannot be updated for other reasons, such as lack of proper file permissions or lack of disk space, the operation continues and all failures are reported.