BuildForge Help

Fixed in This Version

This section lists problems fixed in the current release along with their internal defect tracking numbers.

Agent

RATLC01041967: on Linux, 7.0.2 agent does not install over a 7.0.1 agent
A problem with the RPM spec file made it appear to RPM that the 7.0.2 agent was older than the 7.0.1 agent.

API

RATLC01043511: User cannot add self to new groups
This problem has been resolved.
RATLC01042281: clone() method does not copy project steps
The clone() method now copies project steps.

Documentation

RATLC01049111: URL for locating installation area of Eclipse plug-in is wrong
The URL has been changed to http://<console_host_name>/prism/site.xml. The Build Forge system must be running in order for you to locate this URL from within Eclipse. In the online help, see Accessing Management Console from IDEs with Plug-ins > Plug-ins for Eclipse and Rational Application Developer > Installing the Eclipse or Rational Application Developer Plug-ins.
RATLC01042304 : Multiple entry points for adaptors
Implementing multiple entry points for adaptors requires different methodology starting with Version 7.0.2. See the online help, Integrating with External Applications Using Adaptors > Advanced Adaptors Tasks > Creating Multiple Entry Point Adaptors
RATLC01034596 : Agent source kit, need warning about using -–without-pam to compile
Added warning that using –-without-pam when compiling the agent using the source kit creates an agent with no security. In such a case the agent needs to be installed using a dedicated login and the magic_login authentication needs to be use.
RATLC01045308: Requirements incorrectly state that Solaris on x86 is supported
Removed the statement from the Installation Guide that Solaris on x86 is a supported platform for Management Console.
RATLC01038588: DB2 CREATE statement wrong for setting up DB2 for Build Forge
The incorrect DB2 CREATE statement in the Sample DB2 SQL Command Script has been corrected. See Installation Guide, DB2 Setup, in the installation instructions installing Management Console on Windows and on UNIX/Linux.
RATLC01036029: Microsoft SQL Server setup needs to be based on 2005 version
The instructions for setting up the database were based on the 2000 version. The instructions now use SQL Server Management Studio, the tool in Microsoft SQL Server 2005.

Management Console Engine

RATLC01039403: .break does not stop project if it is in a nested library call
The .break command now stops the project when it is called from a nested library.
RATLC01038462: Build Forge clustered engines can generate identical IDs
Clustered engines now employ UUIDs..
RATLC01042745: Multiple concurrent imports can cause data corruption
This problem has been resolved by using locks and transactions (where they are available, depends on database).
RATLC01039492: Threaded steps calling .runwait fail to complete when the child project completes
This problem has been resolved.
RATLC01039081: Scheduled job using a build tag variable set to 0 causes the build tag variable to be blank in the job log
This problem has been resolved. It was encountered only when a variable used in the build tag was set to zero and the job was started through the scheduler.
RATLC01038770: Purges delete Production-class jobs if both Production and Scratch build records exist
Encountered on Management Console on Solaris 10. This problem has been resolved. This problem was encountered when there was a mix of Scratch and Production build records of the same project when a Production purge ran.
RATLC01037908: Step containing a filter gets PASS status when job is cancelled and job continues to run
This problem has been resolved. Cancelling a job that contains a step with a filter is now handled correctly. The step containing the filter is set to status Cancel, the job status is set to Cancel, and the job is stopped.
RATLC01039525: _USE_BFCREDS ignored by library used to purge a job that used _USE_BFCREDS
This problem has been resolved. The user who started a job using _USE_BFCREDS authenticated properly and the job ran correctly. A library started upon purging that project, that also the _USE_BFCREDS variable, did not use the same user. It used root.
RATLC01038839: .get and .put corrupt files over ~1 MB
This problem has been resolved. Files up to 500 MB have been tested successfully.

Management Console User Interface

RATLC01039392: Job restarts render hidden variables visible in the build log
This problem has been resolved. Hidden variables now show obfuscated values after a restart.
RATLC01045051: unable to move variables within an environment
The problem has been resolved.
RATLC01040842: list variables do not display correctly in the UI when set to "required"
The problem has been resolved.
RATLC01037557: Users with "Delete Group" privilege cannot view details of access groups that they are not a direct member of, but they can delete them
The problem has been resolved. Users must be a member of the group in order to choose the group.
RATLC01037190: Project fields Max Threads and Run Limit are displayed incorrectly when using chain link URL
The problem has been resolved.
RATLC01037118: Step notify dropdowns show inconsistent behavior
The problem has been resolved.
RATLC01034160: Variables and list variables are not correctly interpreted in Schedules environment tab
The problem has been resolved.
RATLC01030035: Cannot sort by Access in Environment menu
The problem has been resolved.
RATLC01038053: LDAP users get added twice with different case upon log in
The problem has been resolved. All LDAP user names get forced to lower case when adding them to Build Forge. This behavior complies with LDAP, which always reports in lower case.
RATLC01049041: magic_login fails to authenticate user with error: unknown account (1)
The problem has been resolved.