TeamForge 19.0 Update 2 Release Notes

Release Information

Issues Fixed in TeamForge 19.0 Update 2 Release

• The event handler that validates the artifact update events, now tracks and logs the details when associations, dependencies, attachments, and tags are added/deleted and when the fields such as Team, Comment Text, and Autosum effort are modified in an artifact.

• Fixed a caching issue that showed non-complying artifact update transactions—that were actually made null and void by custom event handlers—as valid for two minutes.

• When a document flex field was deleted in one of the projects, the value of the same flex field in documents of other projects, was set to “None”. This issue is fixed.

• Fixed a few memory leak issues that occurred during Baseline REST API calls.

• Upgrade to TeamForge-Git/Gerrit version 19.0.15-2.15.14. Bug fixes in Git/Gerrit:

  • The Gerrit project replication process has been tweaked so that the process, by default, is no longer triggered immediately after you restart the Git master server. This helps in quickly bringing up the master server. However, you can set the replicateOnStartup attribute to true in [plugin "teamforge.replication"] section of gerrit.config if required.
  • Active-Passive High Availability Setup for Gerrit is no longer supported.
  • Cleaned up the obsolete gerrit-synch.pid file that was no longer used.

• During an upgrade in a distributed setup, TeamForge provision failed when multiple FQDNs were used for the same server. This is addressed by adding unique service-specific FQDNs for the SCM services such as Git and Subversion. For more information, see TeamForge Services and Domain Configuration Tokens.

Apply TeamForge 19.0 Update 2

TeamForge 19.0 Update 2 is now available. Apply TeamForge 19.0 Update 2 on your site if you are on TeamForge 19.0.

TeamForge add-on packages can remain installed when you apply TeamForge 19.0 Update 2. 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.

The most common Add-ons and their TeamForge compatibility are published here: https://ctf.open.collab.net/sf/go/page1363.

If you have any questions regarding compatibility or updating a specific add-on, contact CollabNet Support.

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 19.0 Update 2 installation repository on sites without Internet access.

   a. Contact the CollabNet Support to get the auxiliary installer package for TeamForge 19.0 Update 2 disconnected installation and save it in /tmp.

   • Red Hat Enterprise Linux/CentOS 7.5 64 bit RPM package: CTF-Disconnected-media-19.0.627-1350.rhel7.x86_64.rpm
   • Red Hat Enterprise Linux/CentOS 6.x 64 bit RPM package: CTF-Disconnected-media-19.0.627-1350.rhel6.x86_64.rpm

   b. Back up the old repo file.

   For example:

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

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

   a. Remove the existing TeamForge repository package.

      yum erase collabnet-teamforge-repo-19.0-1.noarch
   

   b. Contact the CollabNet Support and download the TeamForge 19.0 Update 2 installation repository package to /tmp.

   c. Install the Teamforge 19.0 Update 2 installation repository package.

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

   d. Refresh your repository cache.

      yum clean all
   

4. Install the TeamForge 19.0 Update 2.

   yum install teamforge
   

   The above command installs all the TeamForge updates available in the CollabNet yum repository for TeamForge 19.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 19.0 on a new hardware.

   Update file permissions on your site’s data.

   teamforge apply-permissions
   

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

8. Restart TeamForge.

   teamforge restart
   

[]: