Checking in a project

You can check in a project and, optionally, the sources and products that are members of the project. When checking in a project to a static state, such as integrate, the members of a project must also be non-writable. If the work area is being maintained, run the command on a client that is visible to the work area for the project. Changes made in a visible work area can be automatically synchronized back to the database.

About this task

ccm ci|checkin -p|-project [-s|-state state] [-task task_spec] 
    [-c|-comment comment_string] [-ce|-commentedit] 
    [-cf|-commentfile file_path] [-cr|-commentreplace] [-nc|-nocomment] 
    [-source|-sources [-ss|-source_state source_state]] 
    [-products [-ps|-product_state product_state]] [-projects] 
    [-h|-hierarchy] project_spec...
-c|-comment comment_string
Specifies to append a comment on all baseline projects and their members when they are checked in to the released state. The comment can contain more than one line and accepts backslash encoded values.
You can use this option with -commentedit and -commentfile. If you use the -commentedit option, the comment displays in the default text editor.
-ce|-commentedit
Specifies to invoke the default text editor to compose and edit the comment. The result saved from the text editor is used as the final comment. You can use this option with the -comment and -commentfile options.
-cf|-commentfile file_path
Specifies to use the contents of the specified file for the comment. If you specified -comment, it is appended to that comment. You can use this option with the -commentedit option.
-cr|-commentreplace
Normally, any newly specified comment is appended to an existing comment. Use the -cr option to replace an existing comment. You can replace a comment only on writable objects.
-h|-hierarchy
Applies the check-in scope (for source, products, or projects) to the project hierarchy.
-nc|-nocomment
Do not prompt for comments. If you do not enter a comment for any of the comment options, you are prompted for a comment. The comment is used for all objects checked in by the command. Use the -nc|-nocomment option to suppress comment prompting.
-products
Checks in all the product members of the current project. If -h|-hierarchy is also specified, -products applies to all product members in the hierarchy.
-p|-project
Specifies that any subprojects within the specified project are checked in. If -h|-hierarchy is also specified, all subprojects in the hierarchy are also checked in.
project_spec
Specifies the project to be checked in. See Project specification for details.
-ps|-product_state
Specifies the state for any product objects that are to be checked in. If not specified, the default next state is determined automatically.
Specifies the state of product objects when checking in a product. The product state applies to hierarchical and non-hierarchical check-ins (that is, the -product_state option does not require the -state option).
-s|-state state
Specifies the state for the project to be checked in. If not specified, the default next state is determined automatically.
-source|-sources
Checks in all members of the current project that are source objects. Source objects are files or directories that are not marked as products. If -h|-hierarchy is also specified, all source objects in the hierarchy are checked in.
-ss|-source_state source_state
Specifies the state for source objects when source objects are checked in. If not specified, the default next state is determined automatically.
-task task_spec
Specifies the task to be associated with any source objects that are checked in. A source object is a file or directory that is not marked as a product. You can set task_spec to a single task. See Task specification for details.
Attention: To check in a project version to a non-modifiable state, be sure that all members are in a non-modifiable state already. You cannot check in a project to a non-modifiable state if it has modifiable members.

Example


Feedback