Download 8.0.0.7 Release
March 22, 2018
Buy

IBM Rational Build Forge

Automate and accelerate build and release processes

Rational Build Forge 7.1.3.6

Product Release / Trial | October 17, 2014
This is not the most recent version. We recommend Rational Build Forge 8.0.0.7 . This is made available for archival purposes and may contain bugs and/or security vulnerabilities. If you do download this version, it is being provided AS IS, without warranties of any kind, including the implied warranties of merchantability and fitness for a particular purpose. We strongly advise you review the support pages for this version and update the product or take actions recommended therein. Security bulletins contain instructions for the security vulnerability addressed therein, and may require upgrading to a newer version. Link to security vulnerability blog: IBM PSIRT blog.

Rational Build Forge 7.1.3.6 Release Notes

Fixed APARs

The following APARs are fixed in this release.

APAR

Summary

PI22433DOCUMENTATION DEFECT PROJECT SNAPSHOTS STOP APPEARING IN UI WHEN NO. OF PROJECTS > 1000
PI19874MANAGEMENT CONSOLE DOES NOT START SERVICE LAYER CORRECTLY
PI25567BUILD FORGE IS VULNERABLE TO CROSS SITE SCRIPTING
PI21999PASSWORD AUTOCOMPLETE FEATURE ENABLED
PI12436Job count does not reset after Step cancelled via Management Console
PI11733Unable to use drop down menus in Portuguese
PM84607The sysconfig "Continue Step Parts On Fail" does not work with java/perl engine

Known issues

  • Cannot update BFClient.conf file after upgrade: If the product was installed as a non-root user, you may not be able to update the BFClient.conf file after an upgrade.

    Workaround: Check the owner of the BFClient.conf file. That is normally the same as the non-root user who performed the installation.

  • Problem copying adaptors after upgrade from 7.1.1.x to 7.1.3.x: some adaptor samples were updated for version 7.1.3.1. If you upgrade to 7.1.3.x and then attempt to copy an adaptor that was created before the upgrade, you may see the following error:
    CRRBF0789I: A valid Adaptor Template Identifier must be specified
    

    Workaround: before attempting to copy the adaptor, do the following: open it, rename it, and save it.

  • Agent on AIX 7.1: if steps use absolute paths, the job fails but the steps are listed as passed.

    Workarounds: use one of the following methods.

    • Start the agent using this command. The agent is normally installed in /etc.
      ./bfagent -f /etc/bfagent.conf -s
    • Add a step to the beginning of the project or library and specify a relative path.
  • Incorrect file permissions set for birt when a tomcat user other than root is specified: If you specify that tomcat runs as a user other than root, files for reports and the services plug-ins do not have their permissions set correctly.

    Workaround: change the owner manually (chown) on the following folders and files:

    /birt/configuration/org.eclipse.osgi/.manager/*
    /services-plugins/com.ibm.rational.connector.buildforge.services.plugin/META-INF/*
    
  • Job does not wait for input and never terminates: If you intend to get user input, run the agent in User Mode. Do not run it as a service.
  • Drives mapped with the _MAP trigger variable are not available and the following error message is recorded: "The system cannot find the path specified."

    Workaround: use the "net use" command in every step the requires access to a mapped drive. Example:

    net use X:\\server\share
    

  • Dashboard, License Seats: In Internet Explorer 7 and 8, a limitation in the browser prevents numbers from being shown on this dashboard.
  • Step failure during failover in Oracle RAC: If the Oracle RAC database goes through a failover, a step in progress may fail. Specifically, if the step is performing a write operation when the failover occurs, Oracle RAC might not respond to Build Forge quickly enough for the step state to be determined. This issue was discovered during testing but is considered rare. Build Forge logs grow quickly during a failover as the system continues to poll the database.
  • Password encryption and reinstallation: If you have implemented password encryption and want to preserve user information when you delete and reinstall Build Forge, you must first back up the <bfinstall>/keystore directory and the <bfinstall>/bfclient.conf file. Restore those files in the new installation.
  • Enabling log filters to include entries in the step log: log filters can be applied to the following step log line types: EXEC, RESULT, ERROR, READ, WRITE, MANIFEST, and TMO. When applied, the corresponding step log output lines are included in the filtered results. Log filters cannot be applied to the STEP type. The STEP type is always skipped by log filters.
  • Agent connection issues when using SSL on Solaris: in some cases the console cannot connect to the agent when ssl enabled=yes and password encryption enabled=yes on Solaris. The symptom is a pop-up dialog: AUTH AuthModuleLoadFail.

    Workaround: change the agent port to a port different than the installation port. For example, if the install port is 5555, then change the port to 5557 or other number in the /etc/bfagent.conf and uncomment "port xxxx". Start bfagent using ./bfagent -s.

  • Importing from the UI does not work when using DB2 9.7: in some cases importing from the UI does not work.

    Workaround 1: use the bfimport command line tool.

    Workaround 2: make the DB2Client Library environment variables to the user that the Rational Build Forge server runs as. This can be done in several ways:

    • Export the variables globally.
    • In UNIX and Linux systems, place the variables in /etc/environment.
    • In UNIX and Linux systems, place the variables in /etc/bash_profile or /etc/bashrc (depending on the Linux distribution).
    • In UNIX and Linux systems, place the variables in the user's startup profile (.bashrc).
  • When using token licensing, the message in the console reads "x users logged in" rather than "x of y License Seats Used."
  • Solaris: License error when Build Forge runs as non-root user. If you run Build Forge as a non-root user on a Solaris platform, you may encounter the following message:
    License Error: BuildForge license key is corrupt or missing
    
    Workaround: change the /server/start file to use the following LD_LIBRARY_PATH definition on the su command.
    tomcat_start() {
      if [ -d $TOMCAT_PATH ]; then
         echo "Starting Tomcat"
         rm -f $CATALINA_PID
         su build -c "LD_LIBRARY_PATH=\"$LD_LIBRARY_PATH\"; export LD_LIBRARY_PATH; $TOMCAT_PATH/bin/catalina.sh start"
      fi
    }
    
  • Upgrade does not support installations that have integrated with Websphere Application Server.

    Workaround: use the following procedure.

    1. Uninstall the existing version of Rational Build Forge.
    2. Install the new version of Rational Build Forge. In Installation Manager, in the Database Configuration panel, when you are asked "Do you wish to populate this database at install time," choose No.
    3. Redeploy rbf-services.war.
  • An additional database configuration is needed after upgrading from version 7.1.1.x to 7.1.2.x or 7.1.3.x. Pay special attention to the following items:
    • Re-index your database (in particular, the bf_logs table), for better performance by running bfschema -R.
    • For the IBM DB2 database, re-indexing completes in about 40 seconds per GB. For the Microsoft SQL Server, the operation completes in about one second per GB. For Oracle and MySQL, re-indexing can require significantly more time and possibly a maintenance window.
    • Provided the variability in the operation's duration, the upgrade process does not perform the bfschema -R operation even if you select the option, Do you want the installer to make the required database modifications?.
    • Important: You can run the bfschema -R more than once, but this is not considered a more efficient way to run the re-index operation. It is time consuming and unnecessary.

      If the bf_logs table have the following definitions, you do not need to run the bfschema -R or execute bfschema -R. This command updates the index and key for the bf_logs table.

      • primary key is on bf_result_id and bf_seq
      • unique index idx_bf_logs on bf_logs (bf_id)
      • COLUMN bf_result_ID definition has NOT NULL

      If there is no index BF_BUILDENVOPT_ENVENTRY_SEQ on table BF_BUILDENVOPT, execute the following SQL command:

      • Create the index, BF_BUILDENVOPT_ENVENTRY_SEQ on BF_BUILDENVOPT(BF_ENVENTRY_ID,BF_SEQ);

      If there is no index, BF_ENVOPT_ENVENTRY_SEQ on table BF_ENVOPT, execute the following SQL command:

      • Create the index, BF_ENVOPT_ENVENTRY_SEQ on BF_ENVOPT(BF_ENVENTRY_ID,BF_SEQ);
  • When upgrading, never execute bfschema -R more than once. This issue comes up when performing stepped upgrades sequentially (for example, 7.1.1.4 to 7.1.2 to 7.1.3).

Documentation updates

  • Integrating with IBM HTTP Server requires additional steps. In "Using IBM HTTP Server instead of Apache HTTP Server," the section "Edit the IBM HTTP Server configuration" needs the following changes:
    • Step 4: If you are using an AIX system, use User daemon and Group staff rather than User daemon and Group daemon.
    • After Step 4: Change the permissions on the templates_c file. Use daemon:daemon on Linux systems and daemon:staff on AIX systems.

      Example for Linux systems: chown daemon:daemon /opt/buildforge/webroot/templates_c

  • Documentation for integration with Rational Team Concert: See the Build Forge Team Wiki on jazz.net for complete information about integrating with RTC 2.x and RTC 3.0. Documentation in the Build Forge information center has been updated to clarify differences between integrating with versions 3.x and versions 2.x and 1.x.
  • The Build Forge agent on z/OS uses SystemSSL, not GSKit.

    In "Installing and running the agent on System z platforms", step 4a under the Prerequisites section should be:

    • First step: .configure-zos. Note the use of with-system-ssl. You provide the path to the system SSL. Use the latest version of SystemSSL.

    The code in the example remains the same.

  • The "Continue Step Parts on Fail" table entry in System configuration settings should say:

    Determines the run behavior of multiple commands parts in the same step. When set to the default of No, a failed command part in the step causes the step to fail. When set to Yes, a failed command part does not cause the step to fail. You can run the other commands part in the step. For more information about the command part, see "How the system splits a step into parts" (Developing > Working with steps > Controlling execution flow).