BuildForge can work with Subversion (SVN) for source code
management.
This topic describes additional setup requirements for integrating
with SVN and summarizes the characteristics of the provided sample
adopter templates.
The SVN 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 SVN adaptors
See Adaptor requirements for general requirements. There are no additional
requirements for SVN.
SVN adaptor template samples
The following
adaptor template samples are provided.
- SubversionByDate
- 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.
Variables used:
- SVN_CLIENT
- SVN_OPTS
- SVN_REPOSITORY
- SVN_LAST_REV
- SVN_LAST_DATE
- SubversionByRev
An article describing how to set up this adaptor is on jazz.net: https://jazz.net/wiki/bin/view/Main/RationalBuildForge/SVNAdaptorExample.
- 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.
Variables used:
- SVN_CLIENT
- SVN_OPTS
- SVN_REPOSITORY
- SVN_LAST_REV
- SVN_LAST_DATE