si projectco

CLI Reference > Configuration Management Commands > si projectco

si projectco

checks out members of a project into working files

Synopsis

Description

si projectco checks out project members of a project into working files.

Check out is an operation that extracts the contents of a revision in an archive and copies it to a working file. You can check out any revision by specifying either its revision number or label. By default, the member revision is used. If an existing revision other than the head revision is specified, a branch from that revision is created.

• This command can be only used with the Integrity Lifecycle Manager API. It is supported in the CLI only for the purpose of prototyping Integrity Lifecycle Manager API implementations. It is used to check out Integrity Lifecycle Manager configuration management project members for use in a third party application. To check out project members in a Sandbox, use the si co command.

• If you check out a symbolic link file member, it is stored on the filesystem as a properties file containing a description of the link, rather than as the symbolic link file.

Options

This command takes the universal options available to all si commands, as well as some general options. See the options reference page for descriptions.

• --lineTerminator=[lf|cr|crlf|native]

specifies the line terminator used for the working file. Different operating systems use different characters to indicate the end of a line.

--lf for UNIX, Linux or other Posix systems.

--cr for Mac OS systems.

--crlf for Windows systems.

--native for the line terminator that is native to the client operating system (for example, crlf on Windows, lf on UNIX)

• --[no]branch

controls whether to force the creation of a branch revision. Specifying --branch always creates a branch.

For details on branch revisions, see the si ci reference page.

• --[no|confirm]branchVariant

controls whether Integrity Lifecycle Manager should create a branch off of the revision you are checking out if this is the first time you have attempted to check it out in a particular variant. Specifying --confirmbranchVariant causes a prompt to be displayed so you can confirm the branching.

• --targetFile=value

identifies where to check the member out to

• -l

--[no|auto]lock

• controls whether to create locks on members.

--lock means always lock the member.

--nolock means never lock the member.

--autolock means lock the member based on the locks policy. For information on the locks policy, contact your administrator.

• --lockType=[exclusive|nonexclusive|auto]

specifies the type of lock obtained on checkout.

--lockType=exclusive obtains an exclusive lock on the member. Exclusive locks enable only one member at a time to lock a specific revision.

--lockType=nonexclusive obtains a non-exclusive lock on the member. Non-exclusive locks enable multiple users to check out the same revision for editing.

--lockType=auto obtains a lock on the member based on the locks policy. For information on the locks policy, contact your administrator. If the locks policy does noe require a lock, but the --lock option is set, a non-exclusive lock is obtained.

• --[no|confirm]lockOnFreeze

controls whether to lock the specified member even if it is frozen.

--lockOnFreeze means always do it.

--nolockOnFreeze means never do it.

--confirmlockOnFreeze means always ask before doing it.

• --[no|confirm]downgradeOnLockConflict

controls whether to downgrade your lock to non-exclusive if another user has an exclusive lock on the revision.

--downgradeOnLockConflict means always do it.

--nodowngradeOnLockConflict means never do it.

--confirmdowngradeOnLockConflict means always ask before doing it.

• -u

• --unlock

keeps the member unlocked, and is equivalent to --nolock.

• --[no]update

controls whether to update the project's member revision to the checked out revision.

• --[no|un]expand

controls whether to expand, unexpand, or ignore keywords in the member file. Keyword expansion is only available in text archives, not binary archives. For descriptions of the Integrity Lifecycle Manager keywords, see the Integrity Lifecycle Manager Help Center. Possible keywords are:

$Author: Taherali, Khuzema (ktaherali) $
$CompanyInfo$
$Date: 2017/02/11 15:42:09IST $
$Header: si_projectco.dita 1.3 2017/02/11 15:42:09IST Taherali, Khuzema (ktaherali) Exp $
$Id: si_projectco.dita 1.3 2017/02/11 15:42:09IST Taherali, Khuzema (ktaherali) Exp $
$Locker: $
$Log: si_projectco.dita $
Revision 1.3 2017/02/11 15:42:09IST Taherali, Khuzema (ktaherali)

Revision 1.2 2015/12/01 01:31:47IST Warner, Carrie (cwarner)
XML tagging fixes
Revision 1.1 2015/10/29 10:24:57EDT Flett, David (dflett)
Initial revision
Member added to project /rd/doc/Strategic/xmldocs/en/int-man_pages/si_ref/project.pj
$Revision: 1.3 $
$Name: $
$ProjectLabel: $
$ProjectName: /rd/doc/Strategic/xmldocs/en/int-man_pages/si_ref/project.pj $
$ProjectSetting $
$ProjectRevision: Last Checkpoint: 1.1.1.790 $
$RCSfile: si_projectco.dita $
$Revision: 1.3 $
$SandboxSetting $
$Setting $
$Source: si_projectco.dita $
$State: Exp $

• --[no|confirm]overwriteExisting

controls whether to overwrite an existing target file.

--overwriteExisting means always do it

--nooverwriteExisting means never do it

--confirmoverwriteExisting means always ask before doing it. When asked to confirm overwriting the working file, you have the option of specifying y, n or d. Specifying d displays the differences between the member's working file and the revision that is being checked out.

Specifying the --yes or --no options automatically answers y or n to the confirmation question, and also automatically answers y or n to all questions asked.

• --[no]restoreTimestamp

controls whether to restore the timestamp of the working file to the timestamp of the revision in the member history. If this is not specified, the timestamp is set to the current date and time.

• member...

identifies a specific member; use spaces to specify more than one member.

Diagnostics

See the diagnostics reference page for possible exit status values.

Preferences

Using si setprefs or si viewprefs, you are able to set or view the preference keys for this command.