.scan

.scan [-v][-i <ignorepattern>] baseline | checkpoint
Use the .scan command to enhance the data stored in the BOM for the job. It tracks the files in the step's working directory, along with MD5 values for each file.
.scan baseline
Stores a list of all files in the step's working directory. The system displays the list as a category in the BOM for the job. You can have multiple baseline commands in a job, but each one resets the list to the state of the step's working directory when the command runs. The final BOM displays only one baseline category.
.scan checkpoint
Stores a list of all new, changed, and deleted files since the last .scan baseline or .scan checkpoint command in the job. The system displays the list in the BOM. Each checkpoint command creates a new category in the BOM.
You must use a .scan baseline command before the first .scan checkpoint command in your job. A .scan checkpoint command that precedes a .scan baseline command is ignored.

Command options:

-v
Record a copy of the change information in the job log.
-i
Ignore directories that match the supplied pattern. The pattern can match the beginning, end, or any directory part of the path. You can use this option to eliminate source control directories from change listings.
Example for CVS:
.scan -i CVS checkpoint
The example command keeps CVS directories out of the reports.
Example for Subversion:
.scan -i .svn baseline
If -v is used with -i, the system logs changes to the source control directories but the changes are not included in the BOM.
Note: Do not use more than one .scan command in a single step. The system cannot provide accurate output for the .scan commands if you use more than one in a single step.

For more information about using these commands, see Adding baselines and checkpoints with the .scan command.


Feedback