Creating a Repository

Repository

To evaluate PureCM you can use the 'Example' repository. When you are ready to start working with PureCM you will want to create a new repository. To create a repository go to the Administration view and connect to the server by expanding it in the tree. Right click the server and select the 'Create Repository' menu option. The Repository Wizard will be launched.

Note

Typically you will only have one repository. If you have multiple projects it is usually better to create multiple streams in the same repository for the different projects. This will allow you to share code between the projects using components.

Figure 1.7. Repository Wizard - Details

Repository Wizard - Details

The Details page allows you to choose a title for the repository and the name of the first project.

Press <Next> to Finish. The new repository will be the active repository and will appear under the server in the Administration View.

After creating the repository you may want to modify the changeset reference. By default, each submitted changeset in the repository will be called '[repos name]/[change number]'. You can change this by right-clicking the repository in the Administration View and selecting 'Properties'.

Figure 1.8. Repository Properties - Change ID Format

Repository Properties - Change ID Format

The Change ID Format field allows for the format of changeset IDs to be customised. When a changeset (a group of changes to one or more files) is submitted to the server, the ID specified here will be appended to it.

Table 1.2. Repository Change ID Format

NamePlaceholderDefinition
changes count$n Sequential number of changesets submitted to the repository
day changes count$N Sequential number of changesets submitted to the repository that day (usually used in conjunction with $d$m$y)
stream changes count$t Sequential number of changesets submitted to this stream in the repository
user name$u Name of the user submitting the changeset
user changes count$U Sequential number of changesets submitted to the repository by this user (usually used in conjunction with the above)
client$c Name of the machine submitting the changeset
stream name$s Name of the stream to which the changeset is being submitted
stream path$S Path and name of the stream to which the changeset is being submitted
day$dDD
month$mMM
month$MMonth
year$yYY