Rational Build Forge and StarTeam

BuildForge can work with StarTeam for source code management.

This topic describes additional setup requirements for integrating with StarTeam and summarizes the characteristics of the provided sample adopter templates.

The StarTeam 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 StarTeam adaptors

See Adaptor requirements for general requirements.
  1. Install the StarTeam command-line client on the same host as the agent.
  2. Set up a StarTeam user account for Build Forge to used.
  3. Set up the agent environment so that it can access the client.

StarTeam adaptor template samples

The following adaptor template samples are provided.

StarTeamBaseline
  1. Queries the folder for a StarTeam view to gather information about files.
  2. Writes the following information to the BOM report: file name, status, revision, and branch.

Variables set in the adaptor:

  • USER
  • PASS
  • HOST
  • PORT
  • PROJECT
  • VIEW
  • DIR
  • BFCLIENT

Additional required variables for the environment:

  • P4USER
  • P4PASSWD

You cannot use the Assign Hidden property for these variables. The user and password are written to the step log in clear text.

StarTeamByDate
  1. Uses the StarTeam API to query a StarTeam view to identify changes between the current date and the previous adaptor execution.
  2. Writes the following information to the BOM report: changed files and directories, user, version, date, and change comments.
  3. Writes change details (from diff command output) to the BOM report

Variables set in the adaptor:

  • STA_USER
  • STA_PASS
  • STA_HOST
  • STA_PORT
  • STA_PROJECT
  • STA_VIEW
  • STA_DIR
  • BFCLIENT
  • LASTRUN
  • CURDATE
  • EMAILCHANGES
  • STARTEAM80JAR

Additional required variables for the environment:

  • P4USER
  • P4PASSWD

You cannot use the Assign Hidden property for these variables. The user and password are written to the step log in clear text.


Feedback