BuildForge can work with CVS for source code management.
This topic describes additional setup requirements for integrating
with CVS and summarizes the characteristics of the provided sample
adopter templates.
The CVS adaptor template samples provide methods of analyzing changes
to a baseline. Typically change analysis is used for build avoidance:
if a baseline component has not changed, it is not rebuilt
Additional setup requirements for CVS adaptors
See Adaptor requirements for general requirements. There are no additional
requirements for CVS.
CVS adaptor template samples
The following
adaptor template samples are provided.
- CVSv1Baseline
- Scans a CVS directory on a Build Forge agent for changed files.
- Writes the following information to the BOM report: changed file
name, status, working version, repository version, and sticky tag.
Scans a directory in a ClearCase view.
Variables used:
- CVSv1ByDate
- 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.
Variables used:
- LAST_RUN
- CurDate
- CVSROOT
- MODULE
- BRANCH
- CVSCLIENT
- CVSv1ByTag
- 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.
Variables used:
- LAST_RUN
- CurDate
- CVSROOT
- MODULE
- BRANCH
- LAST_TAG
- CVSCLIENT
- CVSv2ByDate
- 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.
Variables used:
- LAST_RUN
- CurDate
- CVSROOT
- MODULE
- CVSCLIENT