BuildForge Help

Selecting an Adaptor Template

Adaptor templates are provided for several application types: source code, defect tracking, testing, and packaging. Adaptors are classified by the type of application they support.

The Build Forge product provides adaptor templates for the applications in following table. The templates for ClearCase and ClearQuest do not require a separate license key. Other application templates are licensed through the Build Forge Adaptor Toolkit.

Adaptor templates are installed in the following directory:

<bf-install>/interface
Table 1. Adaptor Template Descriptions
Adaptor Template Name Description Type
ClearCaseBaseline.xml

Scans a directory in a ClearCase view.

Writes branch and version information reported by ClearCase to the BOM report.

source
ClearCaseByBaselineActivities.xml

Creates a new baseline from the contents of a ClearCase view.

Compares the new baseline and the baseline from the previous adaptor execution to identify change activity.

For each change activity, writes the following information to the BOM report: activity, files changed, user, date, comments, and version.

For each changed file, writes change details (from diff command output) to the BOM report.

source
ClearCaseByBaselineVersions.xml

Creates a new baseline from the contents of a ClearCase view.

Compares the new baseline and the baseline from the previous adaptor execution to identify changed files.

For each changed file, writes the following information to the BOM report: file name, version, date, user, and comments.

For each changed file, writes change details (from diff command output) to the BOM report.

source
ClearCaseByDate.xml

Queries a ClearCase view for changes between two dates. The default dates are the current timestamp and the timestamp of the previous adaptor execution.

For each changed file, writes the following information to the BOM report: file name, version, date, user, and comments.

For each changed file, writes change details (from diff command output) to the BOM report.

source
ClearCaseByLabel.xml

Creates and applies a new label to the contents of a ClearCase view.

Compares the new label and the label from the previous adaptor execution to identify changed files.

For each changed file, writes the following information to the BOM report: file name, version, date, user, and comments.

For each changed file, writes change details (from diff command output) to the BOM report.

source
ClearQuestClearCaseByActivity.xml

Finds ClearQuest defect records associated with a list of ClearCase activities. For each defect record found, it adds job information to resolve the defect record within ClearQuest if the ClearQuest status allows it to be resolved.

Writes the following information to the BOM report: files associated with ClearCase activity IDs and the ClearQuest defect status.

defect
ClearQuestClearCaseByDate.xml

Queries a ClearCase view for changes between two dates. The default dates are the current timestamp and the timestamp of the previous adaptor execution.

For each changed file, looks for a CrmRequest hyperlink attribute that identifies a ClearQuest change ID. Attempts to resolve the change ID by adding job information to resolve the defect record in ClearQuest if the ClearQuest status allows it to be resolved.

For each changed file, writes the following information to the BOM report: the file name, defect ID, defect status, and any ClearQuest errors.

defect
CVSv1Baseline.xml

Scans a CVS directory on a Build Forge agent looking for changed files.

Writes the following information to the BOM report: changed file name, status, working version, repository version, and sticky tag.

source
CVSv1ByDate.xml

Queries a CVS view for changes between two dates. The default dates are the current timestamp and the timestamp of the previous adaptor execution.

Writes the following information to the BOM report: change type, date, user name, version, and file name.

For each changed file, writes change details (from diff command output) to the BOM report.

source
CVSv1ByTag.xml

Applies a new tag to a CVS module.

Compares the differences between the newly tagged module and a module tagged during the previous adaptor execution.

Writes the following information to the BOM report: file name, revision, state, date, time, change author, and commit comments.

For each changed file, writes change details (from diff command output) to the BOM report.

source
CVSv2ByDate.xml

Queries a CVS view for changes between two dates. The default dates are the current timestamp and the timestamp of the previous adaptor execution.

Writes the following information to the BOM report: change type, date, user name, version, and file name.

For each changed file, writes change details (from diff command output) to the BOM report.

source
PerforceByDate.xml

Queries a Perforce client for changes that occurred since the adaptor execution.

Writes the following information to the BOM report: change, date, time, user, Perforce client, and comments.

Writes change details (from diff command output) to the BOM report.

source
PerforceByRev.xml

Queries a Perforce client for changes that occurred since the last repository revision.

Writes the following information to the BOM report: change, date, time, user, Perforce client, and comments.

Writes change details (from diff command output) to the BOM report.

source
Quota.xml

Queries a folder to determine if any of its subfolders exceed a specified threshold size.

For each subfolder, writes the following information to the BOM report: folder size, owner, and last modified date.

Writes to the BOM report a list of subfolders that exceeded the threshold size.

source
StarTeamBaseline.xml

Queries the folder for a StarTeam view to gather information about files.

Writes the following information to the BOM report: file name, status, revision, and branch.

source
StarTeamByDate.xml

Uses the StarTeam API to query a StarTeam view to identify changes between the current date and the previous adaptor execution.

Writes the following information to the BOM report: changed files and directories, user, version, date, and change comments.

Writes change details (from diff command output) to the BOM report.

source
SubversionByDate.xml

Queries Subversion for repository changes that occurred between a past date and the current date.

Writes the following information to the BOM report: change type, revision, user, file or directory, and change date.

Writes the following information to the BOM report: file name, status, revision, and branch.

source
SubversionByRev.xml

Queries Subversion for changes to a repository that occurred between the current revision and an earlier revision.

For each change, writes the following information to the BOM report: revision, user, change type, file or directory path, and change date.

Writes change details (from diff command output) to the BOM report.

source
VSSByDate.xml

Queries a Visual Source Safe directory for changes between an earlier date and the current date.

Writes change information for projects and files to the BOM report: project or file, version, user, date, time, project activity, file project and action.

Writes change details (from diff command output) to the BOM report.

source