Modifying a release

This subcommand modifies one or more releases.

Before you begin

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

About this task

ccm release -m|-modify [-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] 
        ([(-apr|-add_process_rule|-add_process_rules process_rule_spec)... 
        [-cpr|-clear_process_rules]] | [(-rpr|-remove_process_rule|
        -remove_process_rules process_rule_spec)...]) 
       ([-cct|-create_component_tasks] | [-nocct|-nocreate_component_tasks])
       release_spec...
-active
Sets the release to be active.
-allow_dcm_transfer
Specifies to set the releases as eligible for DCM replication if included by the release scope and query for a transfer set.
-allow_parallel_check_in
Specifies that parallel check-in for objects with this release is permitted. 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. You cannot combine parallel check in without parallel check out.
-apr|-add_process_rule|-add_process_rules process_rule_spec
Adds the specified process rule to each of the releases specified by the arguments. See Process rule specification for details.
-baseline release_spec
Sets the baseline release for the releases being modified. See Release specification for details.
-cct|-create_component_tasks
Specifies to create corresponding component tasks when baselines are created for the release definition being modified. For example, use this option if you are modifying a release definition and know that your team requires component tasks. When you modify the baseline, component tasks are created automatically.
-cpr|-clear_process_rules
Clears any existing process rules before adding a process rule, and sets an absolute set of process rules.
-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.
-groups groups
Specifies the groups that can modify the new release or create following releases from it. The groups value is a list of one or more group names separated by spaces commas.
-inactive
Specifies to set the releases being modified to inactive. Inactive releases cannot be used by developers for development work.
-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_release_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.
-m|-modify
Modifies the specified release.
-noallow_dcm_transfer
Specifies to set the releases as ineligible for DCM replication.
-noallow_parallel_check_in
Specifies that parallel check in for objects with this release is not permitted. 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. You cannot combine parallel check in without parallel check out.
-nocct|-nocreate_component_tasks
Specifies not to automatically create component tasks when baselines are published for the release definition being modified. You can create component tasks manually after a baseline is published for the release. See Creating component tasks for a baseline for details.
-phase phasename
Specifies to set the release phase for the specified releases. The valid release phases are defined in the model attribute. The default values are New, Requirements Definition, Function Definition, Implementation, Validation, and Released.
release_spec
Specifies the releases to modify. See Release specification for details.
-rpr|-remove_process_rule|-remove_process_rules process_rule_spec
Removes the specified process rule from each of the releases specified by the arguments. See Process rule specification for details.

Example


Feedback