BuildForge can work with Perforce for source code management.
This topic describes additional setup requirements for integrating
with Perforce and summarizes the characteristics of the provided sample
adopter templates.
The Perforce 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 Perforce adaptors
See
Adaptor requirements for general requirements.
- Install the P4 command-line client on the same host as the agent.
- Set up a Perforce user account for Build Forge to used.
- Set up the agent environment so that it can access the client.
Perforce adaptor template samples
The following
adaptor template samples are provided.
- PerforceByDate
- 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.
Variables set in the adaptor:
- LAST_RUN
- CurDate
- P4PORT
- BFCLIENT
- P4CLIENT
- FILESPEC
Additional required variables for the environment:
You cannot use the Assign Hidden property for these variables.
The user and password are written to the step log in clear text.
- PerforceByRev
- 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.
Variables set in the adaptor:
- LAST_RUN
- CurDate
- P4PORT
- BFCLIENT
- P4CLIENT
- FILESPEC
Additional required variables for the environment:
You cannot use the Assign Hidden property for these variables.
The user and password are written to the step log in clear text.