Having problems with your account or logging in?
A lot of changes are happening in the community right now. Some may affect you. READ MORE HERE

The checkin command ci

The checkin command ci

The syntax for this command is as follows:
stcmd{Ex} ci [ [–epwdfile “passwordfilepath”] [-p "userName:password@hostName:endpoint/projectName/[viewName/][folderHierarchy/]"] | [-s "userName:password@hostName:endpoint] [-cmp] [-csf] [-encrypt encryptionType]][-rp "folderPath" | -fp "folderPath"] [-filter "fileStatus"] [-l | -u | -nel] [-is] [-ro | -rw]] [-vl "labelName"] [-nomove] [-f NCI] [-o] [-d|-r "comment" | -rf " fileName "][[ -active | [-cr | -req | -task ] processItemPath] [-mark]] [-q|-pf "filterName"] [-ofp "resultsOutputFilePath] [-cp "names"] [files...]

Use ci to check files into a StarTeam repository (or vault) from a working folder using the command line.
You can simultaneously link the new file revisions to a process item. All the files successfully added using
this command will be linked and pinned to the tip revision of the process item. Use the -active option to
specify the currently active process item (previously set using a StarTeam client on your workstation).
If no item is active or you prefer to use another item, use the option that indicates the type of the process
item (-cr, -req, or -task), followed by the complete path from the root folder of the StarTeam project
view to the item, using the forward slash (/) as a delimiter between folder names. For out-of-view process
items, specify the project name and view name in front of the complete folder path. Separate the view path
with a colon (:). For example, -cr MyProject/RootView:ChildView/SourceCode/37 specifies
change request 37 in the SourceCode folder of the ChildView view in the MyProject project.
During execution, the process first assumes that the process item is in the current view, and it checks the
current view to determine whether the full path corresponds to a folder path within that view. If the process item is not found in the current view, it is treated as an out-of-view process item, and the search for the process item begins from the project and view.

Use the -mark option to simultaneously mark the process item as fixed, finished, or complete, depending
on its type.

Parameter Description
-cr, -req, -task Complete path from the project view's root folder to the change request, requirement, or
task number to be used as a process item. Use the forward slash (/) as a delimiter
between folder names.
For out-of-view process items, specify the project name and view name in front of the
complete folder path. For example:
-cr MyProject/RootView/RootFolder/SourceCode/37
This specifies change request 37 in the SourceCode folder (under the root folder) of the
ChildView view in the MyProject project.
Note: For in-view process items, as long as the change request, requirement, or
task numbers are the unique primary descriptors of their types (true by default), it
is sufficient simply to specify the number, with no path. The project and view
names are assumed from -p.
If a process item is specified, then the files being checked in are attached to the process
item and follow the project process rules.
-cr, -req or -task are mutually exclusive. If any one of them is specified, -filter/-f
are ignored.


-cp Name of the code page used for localization and internationalization of the content, file
and folder names, keyword expansion, etc. Supported code page names are US-ASCII
(the default), UTF-8, UTF-16, windows-1252, ISO-8859-1, ISO-8859-9, ISO-8859-15,
windows-31j, EUC-JP, Shift_JIS, ISO-2022-JP, x-mswin-936, GB18030, x-EUC-CN, GBK.


-filter Specifies a string of one or more characters, each of which represents a file status. Never
include spaces or other white space in this string. Only files that currently have the
specified status(es) will be actioned. Does not apply to files that are Not In View.
• C = Current
• M = Modified
• O = Out of date
• N = Not In View
• I = Missing
• G = Merge
• U = Unknown
For example, using CM applies a command only to files with a status of Current or
Modified.
-filter takes precedence over -f NCI. If you use G, O, or U, you must also specify -I
or -o. Otherwise the G, O, or U is ignored.

-f NCI  Identifies files that need to be checked in (Needs Check In)


-i Allows an interactive check-in for files whose status would normally not allow them to be
checked in. You are asked about each file whose status is Merge, Out of Date or
Unknown. You can force the file to be checked in with your response. Alternately, you can
choose to ignore it. Not valid for automated backoffice checkins
If you use the -i option, you cannot use the -o option.


-l Locks the item(s). This is the default when -l, -nel or -u are not used.


-nel Non-exclusively locks a file.


-nomove Do not move labels if already attached.


-o Forces a check-in -o is supported with -filter and -f NCI


-ro Makes the working file read-only after this operation. Without this option, the file remains
as it was prior to the operation. Usually, you use -ro to prevent yourself from editing a file
that is not locked by you. -ro must be used with -l or-u or -nel. If you use -ro, you
cannot use -rw.
-rw Makes the working file read-write after this operation. Without this option, the file remains
as it was prior to the operation. -rw must be used with -l or -u or -nel. If you use -rw,
you cannot use -ro.


-u Unlocks an item.


-vl Specifies a revision label (possibly created earlier using stcmd label) to be applied to the
checked-in files. The label is enclosed in double quotation marks.
Only a revision label may be specified, and it must already exist on the StarTeam Server.


Example
The following example uses ci to check in .bmp files to Online Help, a child of the root folder
StarDraw (in the StarDraw view of the StarDraw project). The command unlocks the files, makes the
working copy read only, and gives the files a revision comment (usually a reason for checking in the files).
Use the -p with ci or the stateful set command to set the context of the project/view/parent folder.
stcmd ci -rp "1024/StarDraw/StarDraw/SourceCode/Online Help" -u -ro -r
"revised for beta" "*.bmp"

DISCLAIMER:

Some content on Community Tips & Information pages is not officially supported by Micro Focus. Please refer to our Terms of Use for more detail.
Version history
Revision #:
1 of 1
Last update:
‎2016-10-04 19:55
Updated by:
 
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.