Creating a release

This subcommand creates a release definition.

To create a release for a new application or component, you can use a unique component name or not use a component name.

To create a release based on a previous release, use the -from option. By default, the new release is created using process rules and other properties that correspond to the properties used in the previous release. It is also a successor of the release on which it is based. The previous release is used as the baseline release.

Before you begin

You must be in the build_mgr or ccm_admin role to use this subcommand.

About this task

ccm release -c|-create [-from release_spec] [-bl|-baseline release_spec] 
        [-desc|-description description] 
        [-desc_edit|-descriptionedit|-description_edit] 
        [-desc_file|-descriptionfile|-description_file file_path] 
        [-manager manager] ([-active] | [-inactive]) 
        ([-allow_dcm_transfer] | [-noallow_dcm_transfer]) 
        [-allow_parallel_check_out] [-noallow_parallel_check_out] 
        [-allow_parallel_check_in] [-noallow_parallel_check_in] 
        [-groups groups] ([-included_releases included_releases] | 
        [-included_releases_file included_releases_file]) 
        [-phase phase] ([-process process_spec] | 
        [(-process_rule process_rule_spec)...]) 
        ([-cct|-create_component_tasks] | [-nocct|-nocreate_component_tasks])
        release_spec
-active
Specifies that the release is active. This setting is the default.
-allow_dcm_transfer
Specifies that the release is eligible for DCM replication if included by the release scope and query for the transfer set. When creating a release for a new component, this defaults to true. When creating a release based on a previous release, the setting for the release, on which the new release is based, is the default.
-allow_parallel_check_in
Specifies that parallel check-in for objects with this release is permitted. This setting is the default when creating a release. When creating a release based on a previous release, the setting for the release, on which the new release is based, is the default. You cannot combine parallel check in without parallel check out.
-allow_parallel_check_out
Specifies that parallel check-out for objects with this release is permitted. This setting is the default when creating a release. When creating a release based on a previous release, the setting for the release, on which the new release is based, is the default. You cannot combine parallel check in without parallel check out.
-baseline release_spec
Specifies the release used as the baseline for the new release. When creating a release based on a previous release, that previous release is used as the baseline by default. When creating a release for a new component, the default baseline release is blank.
-cct|-create_component_tasks
Specifies to create corresponding component tasks when baselines are created for the release definition being created. For example, use this option if you are creating a release definition and know that your team requires component tasks. When you create the baseline, component tasks are created automatically. This setting is the default.
-desc|-description description
Specifies the description for the release. You can use escape sequences to include newlines and other characters. Alternatively, use the -description_file or -description_edit for specifying multi-line descriptions. If -description, -description_file and -description_edit are all used together, the description takes the -description option value, appends the description read from the file specified by -description_file, and starts the current default text editor to show the comment. The text saved from the editor is then used for setting the description.
-desc_edit|-description_edit
Starts the current text editor to allow the release description to be interactively edited or composed. The saved result from the text editor is used to set the description. See -desc|-description.
-desc_file|-description_file file_path
Specifies a path to a file containing a description.
-from release_spec
Specifies the release on which the new release is based. When creating a release based on a previous release, many of the new settings for the release are copied from the previous release. The previous release is used as the baseline release by default.
-groups groups
Specifies the groups that can modify the new release or create following releases from it. When creating a release based on a previous release, the new release uses the same groups as the release on which it is based by default. The groups value is a list of one or more group names separated by spaces commas.
-inactive
Specifies that the new release is inactive. Inactive releases cannot be used by developers for development work. By default, new releases are created as active releases.
-included_releases included_releases
Specifies one or many releases to be included in the release. This string supports multiple releases separated by a comma, and optionally, spaces. The comma is required; however, releases with leading or trailing spaces are not supported. Alternatively, you can use the included_releases_file option and enter data from a file.
Included releases are used by default for object status-based updates only. Included releases are used to weight the selection scoring while update members is running.
-included_releases_file file_path
Specifies a path to a file containing the releases to be included.
-manager manager
Specifies the product or component manager for the release. The default on create is the user who is creating the release definition, and can be a one-line string only.
-noallow_dcm_transfer
Specifies that the release is not eligible for DCM replication. When creating a release for a new component, the release is eligible for replication by default. When creating a release based on a previous release, the setting for the release, on which the new release is based, is the default.
-noallow_parallel_check_in
Specifies that parallel check-in for objects with this release is not permitted. Parallel check-in is allowed by default when creating a release. When creating a release based on a previous release, the setting for the release, on which the new release is based, is the default. You cannot combine parallel check in without parallel check out.
-noallow_parallel_check_out
Specifies that parallel check-out for objects with this release is not permitted. Parallel check-out is permitted by default when creating a release. When creating a release based on a previous release, the setting for the release, on which the new release is based, is the default. You cannot combine parallel check in without parallel check out.
-nocct|-nocreate_component_tasks
Specifies that component tasks are not automatically created when baselines are published for the release definition being created. You can create component tasks manually after a baseline is published for the release by using the Creating component tasks for a baseline subcommand.
-phase phasename
Specifies the release phase for the new release. By default, a new release is created with release phase New. The valid release phases are defined in the model attribute. The factory default values are New, Requirements Definition, Function Definition, Implementation, Validation, and Released. The specified value must match one of the valid release phase values and is case-sensitive.
-process process_spec
Specifies a process for a release as it is being created. The release-specific process rules associated with the generic process rules for the specified process are associated with the new release. If any of the release-specific process rules do not exist, they are created.
release_spec
Specifies the name of the new release to create.

Example


Feedback