Borland^® Gauntlet™ 2007 Release Notes
Version 1.0

This file contains important information. Read this file in its entirety.

System Requirements/Prerequisites

Following are the system requirements for installing and running Gauntlet.

Hardware Recommendation

Note: The build requirements of the applications you develop can create additional hardware requirements.

Gauntlet Server Disk Space

Disk space requirements for a Gauntlet server vary significantly based on the following:

• Frequency and size of builds
• Amount of source code
• Resources for managed applications
• Frequency of revisions to source code

See the Help topic titled Build Output for information about setting disk space limits.

Operating Systems and JDKs tested with Gauntlet 2007

• Microsoft® Windows® XP (32-bit version)
• Microsoft® Windows® 2003 Server (32-bit version)
• RedHat® Linux version 4, kernel 2.6.9-34 (32-bit version), with libldap-2.2.so.7
• Sun Microsystems Java SE Development Kit 1.5 Update 8 (jdk-1_5_0_08)

Java Tools

Gauntlet 2007 ships with JUnit 4.1 and Ant 1.7.

Tips for Optimizing and Tuning Your Gauntlet Installation

The following are tips that can help you maintain the efficiency of your Gauntlet installation.

• Monitor your disk space usage periodically to be sure you have adequate space. You can set size limits for saved data on each repository to help control disk space usage.
• For optimal performance, do not run a virus scanner on the Gauntlet server.
• For optimal performance, move your Gauntlet_storage directory to a separate physical disk from the Gauntlet installation.
• Gauntlet uses Subversion hook logic. If your site has an existing Subversion installation and you replay your data into Gauntlet, the Gauntlet hooks are used. This means that any custom hook logic you created will no longer be used. You can add your custom hook logic to the Gauntlet hooks. Typically, you add your custom pre-commit hooks before the Gauntlet pre-commit hooks, and your custom post-commit hooks after the Gauntlet post-commit hooks.
• Gauntlet maintains an access file for its Subversion instance. If your site has an existing Subversion installation and you replay your data into Gauntlet, you must enter your users in the Gauntlet interface so Gauntlet is aware of them.

Known Issues

The following are known issues in Gauntlet.

• When you perform a backup on a Windows platform, you can safely ignore warning messages similar to the following: pg_dump: [custom archiver] WARNING: ftell mismatch with expected position -- ftell used.
• Before you can use any command-line tools, you must start the Gauntlet services (Windows) or run the startstack executable (Linux).
• In a StarTeam replay, files that were deleted from StarTeam during the period being replayed cannot be replayed into Gauntlet.
• For the SCTM extension, Gauntlet gets a URL link from the SCTM Web services and puts it in the SCTM report as a link. If you logged on to SCTM locally with a URL in the form localhost/…, the link does not work.
  WORKAROUND: Log on to SCTM with the actual host name instead of localhost.
• If you manipulate the Gauntlet URL from outside the Gauntlet Dashboard, for example by clicking the browser Back button or the link in a Gauntlet email notification. it is possible for the list of revisions and the revision detail display to be out of sync. Gauntlet refreshes the list of revisions based on the filters in effect, but the revision detail display is based on the URL. In this case, that URL may point to a revision that is not on the list of revisions.
• To run a StarTeam replay from an encryption-enabled Linux system, you must copy jsafePure.zip from the StarTeam 2005 R2 Universal client lib directory and place it in {Gauntlet_home}/usr/tomcar/shared/lib. You must restart Gauntlet for this to take effect.

Known Documentation Issues

There are no known documentation issues at this time.

Getting Information

For more information or to get help, visit the Gauntlet forum at http://answers.borland.com. Under the heading Discuss in the Forums, click Application Lifecycle Products, and then click Gauntlet.

Top

Installation Instructions

For information about installation, see Install.htm. The default location is Borland\Gauntlet2007