Project registers are distinct from ordinary registers. They persist
across builds and can be created and viewed through the Management Console
interface, making them an ideal way to store some kinds of configuration information.
For example, you could store an IBM® Rational® ClearCase® config
spec as a project register, then have a step use a .pop -p command
to extract the specification and use it with a cleartool setcs command,
configuring your build. This allows you to manage the configuration along
with the project.
If you have a project register named ALPHA, you could also have an ordinary
register named ALPHA, with entirely different contents. Project registers
are a separate set of values.
You can create and access project registers in two ways:
- Through dot commands (.push and .pop),
by adding a -p option. When you use the -p option, your command refers to
a project register, rather than an ordinary register.
For example, a command
.push -p ALPHA register.txt
places
the contents of the file register.txt in the project register named ALPHA.
- Through the Management Console interface. Select Projects,
then click the
icon next to the desired project's name.
The project properties appear in the lower pane; click the Registers tab
to display the project's registers. The tab provides a form for managing registers:
- To create a new register, enter a name and contents, then click Create.
- To delete a register, click the trash can icon next to the register's
name in the list at the right of the form.
- To edit a register, click the
icon next to the
register's name in the list. The system populates the register form with
the register's contents. Make your changes, then click the Save
Edited Register button.
Anyone who has access to a project can view and edit its project registers.
Note: Use uppercase to create register names and to reference all register
types. Even though you can create registers using lowercase letters, registers
are stored and must be referenced using uppercase letters.