CollabNet TeamForge 17.11 Update 1 release notes

Released on: May 16, 2018

TeamForge 17.11 version history

  • TeamForge 17.11 GA: 17.11.455 (11/10/2017)
  • TeamForge 17.11 Update 1: 17.11.501-841 (05/16/2018)

About TeamForge 17.11 Update 1

Fixed issues
  • Using certain keywords such as tracker, docman, planning, frs, taskmgr, scm, wiki, and discussion in planning folder names (for example, "Metric tracker") caused an error. In addition, the planning folder ID was not shown in the Jump to ID field. This is fixed.
  • Fixed an issue with Oracle CLOB data handling that prevented the TrackerIncrementalJob from running post TeamForge upgrade.
  • A cross-site scripting vulnerability was observed on Tracker search page whenever you save a search with invalid search name. This is fixed.
  • Fixed an issue that allowed users to upload restricted file types on the Project Home page.
  • Removed the legacy CSRF token from TeamForge.
  • SSL warnings or errors were not ignored even if the ignoreSslWarnings property was set to true while configuring SCM webhooks. This is fixed.
  • A ClassNotFound exception was thrown when using SOAP60 SDK jar in CollabNet Desktops - "Eclipse" and "GitEye". This was due to the missing SfQName.class file in SOAP60 SDK jar file. This exception is handled and the issue is fixed now.
  • Some custom reports were not generated due to an issue in the CLI server. This is fixed.
  • Handled the API call that duplicated the information obtained by the original API call, when viewing the Git commits in the code browser. This fix has resulted in much quick response time.
  • During an upgrade, TeamForge provision failed due to the issue found in the Gerrit database backup directory creation for subsequent provisions. This is fixed.
  • Fixed the issue in which the open cursor and connection pool errors were reported due to which the TrackerIncrementalJob failed.
  • For SCM users, reports were not displayed on their Project Home page. This issue is fixed.
  • "Delete" button was not shown for any of the components added on the Project Home page of SCM users.
  • When a SCM user tried to create project using a project template, a TeamForge system error was thrown. This issue is fixed.
  • Associations were not displayed properly due to an issue in storing the Commit ID for some TeamForge commit events in EventQ. This is fixed.
  • While checking the domain names, the DNS lookup was not done via the /etc/hosts/ file as expected. Due to this, a TeamForge System error was reported and the Commit Activity Reports were not generated. This issue is fixed with the following workaround:
    Here, the reports do the DNS lookup in the opt/collabnet/teamforge/var/cliserver/etc/hosts> file instead of the DNS server.
    • cp /etc/hosts/ /opt/collabnet/teamforge/var/cliserver/etc
    Note: For any changes in /etc/hosts/ file, make sure that you copy the /etc/hosts/ file to /opt/collabnet/teamforge/var/cliserver/etc/.
  • Due to insufficient PGA memory, the XML to Non-XML conversion process failed. This issue is fixed by resetting the PGA_AGGREGATE_LIMIT attribute value to '0'.
Upgrade to Gerrit 17.11.17-2.14.8 that provides the following fixes:
  • Not all the tags associated with a Git commit were shown on the Code Browser. This issue is fixed.
  • When a pull request merge was done on different commits of the same submodule on different branches, the merge contained the commits of an older version of the submodule.
  • An error was thrown, if the destination branches in the Code Browser had the URL encoded character "+" in their pull requests. This is resolved.
  • Performance has been improved when viewing reviews and tags on repositories having large number of tags.
  • Fixed the performance issue that led to the delay in loading source code repositories.
  • The maxRetries configuration parameter was ignored by TeamForge-Git integration resulting in indefinite updates to disconnected remote replica servers. This issue is fixed.

Apply 17.11 Update

Click here to apply the latest 17.11 update.