Skip to main content
Version: TeamForge 24.1

TeamForge 24.1 Update 1 Release Notes

Release Information

VersionReleased On
GA Version: 24.1.0.146Jan 31, 2025
Update 1: 24.1.0.157Jul 25, 2025

Issues Fixed in Teamforge 24.1 Update 1 Release

  • Fixed an issue where artifacts did not appear in the planning folder view for users with tracker-level view permissions in older trackers. This occurred in both Sort and Rank modes and resulted in a persistent loading spinner. The logic now correctly displays artifacts users are permitted to see and improves performance in planning folders with many subfolders.
  • Fixed an issue that prevented the Project Admin section from loading when a project lacked the required tool preference setting. Affected projects displayed a server error instead of the configuration menu after upgrading to version 24.1.
  • Fixed an issue where JBoss memory was not released efficiently during concurrent CLI-based downloads of large builds. This caused performance issues in high-load environments. Memory handling for download streams has been optimized.
  • Fixed a concurrency issue that caused status changes to fail when multiple users updated the same artifact simultaneously. The update logic now handles concurrent edits more reliably.
  • Fixed an issue where Excel files downloaded from Collab DOC could not be opened due to unsupported characters in the file name. File naming has been updated for compatibility with newer versions of Microsoft Excel.
  • Fixed a security issue where the version of Log4j bundled within gerrit.war was flagged as vulnerable during a security scan. The Log4j dependency has been updated to a supported version to address the reported vulnerability.
  • Fixed an issue where users who could not submit a pull request were not seeing updated repository content. The system now calls the refresh repository endpoint to ensure users always see the latest data.
  • Fixed an issue where users could create or update repositories with invalid .gitmodules files through the UI or REST API. Such corrupted files previously caused push failures over SSH and HTTPS due to unpack errors.

TeamForge SCM—Enterprise Version Control

TeamForge—Git Integration 24.1.6-3.7.9_1

For more information about vanilla Gerrit version 3.5, see Gerrit 3.5 Release Notes.

Apply Teamforge 24.1 Update 1

Teamforge 24.1 Update 1 is now available. Apply Teamforge 24.1 Update 1 on your site if you are on Teamforge 24.1.

TeamForge add-on packages can remain installed when you apply Teamforge 24.1 Update 1. No updates are required. However, you should verify the compatibility of Add-ons applied to your site as some may be more specific to your site.
If you have any questions regarding compatibility or updating a specific add-on, contact Digital.ai Support.

important

You must log in as a root user to apply Teamforge 24.1 Update 1.

  1. Stop TeamForge.

    note

    Stop TeamForge on all the servers in a distributed setup.

    teamforge stop
  2. Skip this step if your site has internet access. This step is to configure Teamforge 24.1 Update 1 installation repository on sites without Internet access.

    a. Contact the Digital.ai Support to get the auxiliary installer package for Teamforge 24.1 Update 1 disconnected installation and save it in /tmp.

    • Red Hat Enterprise Linux/CentOS 7.9 64 bit RPM package: CTF-Disconnected-media-24.1.357-xxx.rhel7.x86_64.rpm
    • Red Hat Enterprise Linux 8.8 64 bit RPM package: CTF-Disconnected-media-24.1.357-xxx.rhel8.x86_64.rpm

    b. Back up the old repo file.

    For example:

    mv /etc/yum.repos.d/CTF-Disconnected-media-24.1.356.repo /etc/yum.repos.d/CTF-Disconnected-media-24.1.356.repo.cn_backup

    c. Unpack the 24.1 Update 1 disconnected installation package.

    rpm -Uvh <package-name>

    d. Verify your yum configuration files.

    yum list httpd
    yum list apr
  3. Configure your TeamForge installation repository. This step is to configure Teamforge 24.1 Update 1 installation repository on sites with Internet access.

    a. Remove the existing TeamForge repository package.

    yum erase collabnet-teamforge-repo-24.1-0.noarch

    b. Contact the Digital.ai Support and download the Teamforge 24.1 Update 1 installation repository package to /tmp.

    c. Install the Teamforge 24.1 Update 1 installation repository package.

    yum install -y /tmp/collabnet-teamforge-repo-24.1-0.noarch.rpm

    d. Refresh your repository cache.

    yum clean all
  4. Install the Teamforge 24.1 Update 1.

    yum install teamforge

    The above command installs all the TeamForge updates available in the CollabNet yum repository for Teamforge 24.1.

  5. Check the /opt/collabnet/teamforge/var/scm/gerrit/gitroot directory. If it is empty, remove it manually.

    rm -rf gitroot
  6. Deploy services.

    teamforge provision
  7. Update file permissions on your site's data.

    important

    Do this if and only if you are upgrading from TeamForge 17.1 (or earlier) to 24.1 on a new hardware.

    teamforge apply-permissions
    note

    This process can take a long time on sites with a lot of data.

  8. Restart TeamForge.

    teamforge restart