Here's a list of few noteworthy issues fixed in TeamForge 19.0 Update 1 and the instructions to apply TeamForge 19.0 Update 1.

Release Information

  • Released on: May 16, 2019
  • Update 1 Version: 19.0.595-1332

Issues Fixed in TeamForge 19.0 Update 1 Release

  • Fixed an issue that displayed the Task Board statuses in reverse/incorrect order.
  • Post upgrade to TeamForge 19.0, deleting the flex fields in one Tracker of a given project cleared the values of the flex fields in the artifacts of other Trackers in the project. This issue is fixed.
  • Fixed the issue where unauthenticated users were able to access Baseline Packages.
  • Fixed the issue that prevented the Tracker table reports from being edited.
  • A new deploy hook script has been added to filter repositories with incorrect permissions (at the top level) and apply correct permissions on those repositories.

  • TeamForge CLI—Bug Fixes and Enhancements

    • Fixed the version check failure with 1.9.10
    • Fixed the Select filter command failure
    • Allow multiple values in multi-select field set command
    • Addition and removal of SOAP50 references
  • The Show Traceability View toggle button (in the Associations tab on the View Artifact page) was not working. This is fixed.
  • Postgres connections exhausted when a Baseline REST API, which runs a GUI script to create multiple projects, was called. This issue is fixed.
  • Fixed the high CPU utilization issue observed on the server where baseline services were hosted.
  • Baseline creation failed for baselines that included source code repository filters with long tag names. This issue is fixed.
  • A database query error was thrown due to the mismatch in the number of records copied from TeamForge to Baseline database, during repeated baseline creations sequentially. This issue is resolved.
  • Baseline workflow page was not refreshed/reloaded automatically after deleting a workflow. This is fixed.
  • Few Baseline Packages having references to source code repositories didn’t contain the actual source code data. This is fixed.
  • Fixed the issue due to which Phoenix (daemon) failed to start up during TeamForge provision after an upgrade.
  • The refresh timeout logic for the Replicas tab has been modified so that the timeout happens immediately after the tab is refreshed/reloaded.
  • Fixed an issue due to which the source code page kept on loading without showing the contents.
  • Sorting the repository list was limited to the current page in cases where the list of repositories spans multiple pages, which is now fixed.

  • Baseline Field Inclusions configuration went missing in the projects created from template via the SOAP API call. This issue is fixed.

    Limitation: For multiple project creation requests via the same template, the SOAP API returns response only for the first request, even though the requested projects are created.
  • When a Baseline Package was generated without the manifest fields configured, the baseline service was brought down without throwing an appropriate error message. This issue is fixed.
  • Gerrit service initialization and SCM integration registration failed, if the site-options.conf tokens SECURE_REDIRECTS=true and ALLOWED_HOSTS were enabled. This is fixed.
  • Upgrade to Gerrit 19.0.10-2.15.13.

Apply TeamForge 19.0 Update 1

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

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

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. 
    teamforge stop

  2. Skip this step if your site has internet access. This step is to configure TeamForge 19.0 Update 1 installation repository on sites without Internet access.

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

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

    b. Back up the old repo file.

    For example:

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

    c. Unpack the 19.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 19.0 Update 1 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 1 installation repository package to /tmp.

    c. Install the Teamforge 19.0 Update 1 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 1.

    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. Update file permissions on your site’s data.

    teamforge apply-permissions

  8. Restart TeamForge.

    teamforge restart

[]:

Tags for this page: ctf_19.0 release_notes