si viewprojecthistory

CLI Reference > Configuration Management Commands > si viewprojecthistory

displays a history of the project

Synopsis

si viewprojecthistory [--fields=field1[:width1],field2[:width2]...] [--height=value] [--width=value] [-x value] [-y value] [(-P project|--project=project)] [--[no]failOnAmbiguousProject] [--rfilter=filteroptions] [(-S sandbox|--sandbox=sandbox)] [--devpath=path] [--projectRevision=rev] [--hostname=server] [--port=number] [--password=password] [--user=name] [(-?|--usage)] [(-F file|--selectionFile=file)] [(-N|--no)] [(-Y|--yes)] [--[no]batch] [--cwd =directory] [--forceConfirm=[yes|no]] [(-g|--gui)] [--maxTrunkRevs=value] [--[no]persist] [--quiet] [--settingsUI=[gui|default]] [--status=[none|gui|default]][--[no]hideCheckpointsOnInactiveVariants]

Description

si viewprojecthistory displays a history of the project, including information on each historical checkpoint. For example:

si viewprojecthistory --project=c:/Aurora_Program/bin/Libra/project.pj

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.

• --fields=field1[:width1],field2[:width2]...

allows you to select fields to be printed, specified in the format field1[:width1],field2[:width2].... Specifying the column [:width] (in pixels) for each field is optional - widths are only available with the -g or --gui options. Under the CLI the fields are separated with a space.

The fields available for printing can be one or more of the following:

◦ associatedIssues

displays the ID and summary of any Integrity Lifecycle Manager items associated with the project. Only item types that you have permission to view are displayed.

◦ author

displays author names.

◦ date

displays the project checkpoint date.

◦ description

displays checkpoint and project descriptions.

◦ labels

displays labels.

◦ revision

displays the checkpoint number.

◦ state

displays the checkpoint state.

• --[no]persist

controls whether this presentation of information should continue to be updated as new information becomes available. --nopersist forces a static "snapshot" of information, while --persist gives real-time updates.

• --rfilter=filteroptions

allows you to display any checkpoints of the current project that meet the selection criteria specified in the filteroptions. Comma separated expressions are combined using an OR operator. Multiple occurrences of an option are combined using an AND operator. A leading ! negates any simple filter that follows. For example,

--rfilter=labeled:Release 3.0,branchboundaries --rfilter=!labeled:obsolete

displays all checkpoints with a label of "Release 3.0" or at a branch boundary and whose label is not "obsolete". The filteroptions can be one or more of the following:

◦ range:low-high

selects checkpoints that are in the specified number range. If required, you can specify just one end of the range. The range includes the low and high values. To specify multiple ranges, the range keyword must be repeated, for example --revisionFilter=range:1.100-1.200,range:1:400-1:500

◦ branchrange:low-high

selects branched checkpoints that are in the specified number range. If required, you can specify just one end of the range. The range includes the low and high values. To specify multiple ranges, the branchrange keyword must be repeated, for example --rfilter=branchrange:1.2.1.1-1.2.1.5,branchrange:1.4.1.1-1.4.1.5

◦ daterange:<date>-<date>|:past:<nb>:years|months|days|hours

selects checkpoints that were created during a specified time range or during a specified amount of time in the past. <date> specifies a date in any of the local date/time formats. For more information on date/time formats, see the options reference page. <nb> is used to specify the number of units to include in the range for a specified amount of time in the past.

If the date/time format contains either "-" or "," you must quote each date. For example: --rfilter=daterange:"June 21, 2005 - 6:07:28 PM"-"June 25, 2005 - 6:07:28 PM"

When in a shell, you must use two kinds of quotes so that the shell does not remove them. For example: --rfilter=daterange:'"June 21, 2005 - 6:07:28 PM"'-'"June 25, 2005 - 6:07:28 PM"'

--rfilter=daterange:"'June 21, 2005 - 6:07:28 PM'"-"'June 25, 2005 - 6:07:28 PM'"

◦ devpath[::current|:name]

selects checkpoints that are on the specified development path.

◦ branch[::current|:name]

selects checkpoints that are on the specified branch.

◦ labeled:name

selects checkpoints with labels. If a label name is specified, only checkpoints with that label are displayed. If no label name is specified, all labeled checkpoints are displayed.

◦ labellike:pattern

selects checkpoints that match the specified pattern. Your administrator determines whether glob or regex patterns are used for matching.

◦ state:name

selects checkpoints that are at the specified state.

◦ author[::me|:userName]

selects checkpoints created by the specified author.

◦ anyspecial

selects base project checkpoints.

◦ branchboundaries

selects checkpoints that are branched, or at the base or tip of a branch.

• --maxTrunkRevs=value

specifies the maximum number of checkpoints along the mainline project to display. If you limit the number of checkpoints to be displayed, and the maximum is reached, a trailing message displays at the bottom of the list. The maximum number of checkpoints is based on the number of visible mainline checkpoints; branched checkpoints are not included in the count.

• --[no]hideCheckpointsOnInactiveVariants

controls whether checkpoints for inactive development paths are hidden. --nohide shows these checkpoints, while --hide hides them. If you do not set this option, checkpoints for inactive development paths are shown.

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.