BuildForge Help

.scan

.scan [-v][-i <ignorepattern>] baseline | checkpoint
The .scan command enhances 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. Use the command in one of two forms:
.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 .baseline command executes. 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. As with the .scan baseline command, the system displays the list in the BOM, but each checkpoint command creates a new category in the BOM. You must issue 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.

The command has two options:

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 on using these commands, see Using the Bill of Materials.