Skip to main content
Version: TeamForge 23.0

TeamForge 23.0 Update 1 Release Notes

Release Information​

VersionReleased On
GA Version:
23.0.192		Jun 20, 2023
Update 1:
23.0.236-413		Nov 30, 2023

What's New in TeamForge 23.0 Update 1 Release​

Enhanced Search to Select Binaries for Baselining​

You can now search for specific packages (instead of loading all the packages upfront) using the enhanced binary package search function and select them to be a part of your baseline. This search and select function comes in handy when your project consists of a large number of packages to search from. In addition, this enhances the overall TeamForge performance as you do not have to load all the available packages while you create baselines.

You can locate files or components by entering either the full file path or a partial path in the Select Packages component search box, which then filters and displays only the relevant packages in the Available Packages area for you to choose from. Select Packages component search

Baseline Service Monitoring​

You can now actively monitor baseline services in real-time with monit. Monit performs automated checks every 5 minutes, and in the event of a service failure, it initiates a restart for baseline servers, ensuring the continuous and faultless functionality of baseline services.

Copy URL on Document View Page​

You can now copy the document URL to download a document by using the Copy Url icon on the respective document view page. This functionality eliminates the need for manual generation of such links.

New Documents URL Format​

The new document URL format now includes only the document ID when you move or rename a document's title or folder.

Issues Fixed in TeamForge 23.0 Update 1 Release​

  • The Documents module is enhanced to address the following issues:
    • Fixed—The Last modified by and Created by links on the document description page now takes you to the user details page.
    • Fixed—Project members with document edit permission can now download locked documents on documents list and view pages.
    • Fixed—The document tree now displays the document folder name instead of using ellipses when the name contains a large number of characters.
    • Fixed an issue that prevented users from downloading documents when the document name contained special characters.
    • Fixed an issue that prevented advanced search from retrieving the document folder’s details.
    • Fixed an issue with document downloads due to which the active version of a document was downloaded instead of the latest version.
    • Fixed an issue that caused a permission denied error in the windows desktop client for documents with View, Edit, or Create role permissions.
    • Fixed the web browser context menu as follows:
      • The web browser context menu now displays Open link in new tab and Save link as options when you right-click the document folder link.
      • The web browser context menu now displays Save link as option when you right-click the document icon, title, or previous version inside the document folder.
    • Fixed—When you navigate to a nested folder document within a large folder tree on the left navigation bar of the document or planning folder, now points the selected folder instead of resetting to the top.
    • Fixed—When you download a document using the old document download URL, it now redirects to the new document URL.
  • Fixed an issue with the POST /documentfolders/{docfolderid}/documents API call that caused the sample payload to fail when creating a document.
  • Fixed an issue in the View Report page that prevented downloading the report images.
  • Fixed an issue that prevented the new text page component from displaying an image when you copied and pasted an image into it, even if the image name contained special characters.
  • Fixed an issue that caused an unexpected alert message when adding a text component with HTML content into a project home.
  • Fixed an issue in the tracker settings that caused a tracker field to remain in REQUIRED status even after deleting the workflow-related status in tracker settings.
  • Fixed an issue that led to high CPU utilization when the baseline creation count was increased in the baseline server.
  • Fixed—After upgrading to TeamForge release 23.0, HTML editing displayed HTML codes instead of text components in the project home.
  • The artifact ASSOCIATIONS tab now displays the document version of the associated document.
  • Fixed an issue that prevented newly created Gerrit custom labels from displaying in the UI and impeding the full functionality of Gerrit.

Apply TeamForge 23.0 Update 1​

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

TeamForge add-on packages can remain installed when you apply Teamforge 23.0 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 23.0 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 23.0 Update 1 installation repository on sites without Internet access.

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

    • Red Hat Enterprise Linux/CentOS 8.6 64 bit RPM package: CTF-Disconnected-media-23.0.236-413.rhel8.x86_64.rpm
    • Red Hat Enterprise Linux/CentOS 7.9 64 bit RPM package: CTF-Disconnected-media-23.0.236-413.rhel7.x86_64.rpm

    b. Back up the old repo file.

    For example:

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

    c. Unpack the 23.0 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 23.0 Update 1 installation repository on sites with Internet access.

    a. Remove the existing TeamForge repository package.

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

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

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

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

    d. Refresh your repository cache.

    yum clean all

  4. Install the Teamforge 23.0 Update 1.

    yum install teamforge

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

  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. important

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

    Update file permissions on your site's data.

    teamforge apply-permissions

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

  8. Restart TeamForge.

    teamforge restart