TeamForge 20.0 Update 1 Release Notes

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

Release Information

Released on: Feb 27, 2020
Update 1 Build: 20.0.321-620

Issues Fixed in TeamForge 20.0 Update 1 Release

The scmadmin password was not URL encoded while cloning a repository and as a result any special characters in the scmadmin password prevented creation of projects from baselines that consist of SCM (Subversion/CVS) or Git repositories. The scmadmin password is now URL encoded.

Unlike in the past, in case of HTTP 503 - StatusServiceUnavailable response, the WEBR’s sender process keeps retrying to deliver the message to the webhook endpoint until it succeeds. For more information, see TOPIC Event Type.

Fixed an issue due to which the time taken to migrate the baseline data was longer than usual (due to the creation of duplicate indexes).

Apply TeamForge 20.0 Update 1

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

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

Important: You must log in as a root user to apply TeamForge 20.0 Update 1.

Stop TeamForge.
Note: Stop TeamForge on all the servers in a distributed setup.
```
teamforge stop
```
Skip this step if your site has internet access. This step is to configure TeamForge 20.0 Update 1 installation repository on sites without Internet access.

a. Contact the CollabNet Support to get the auxiliary installer package for TeamForge 20.0 Update 1 disconnected installation and save it in /tmp.
- Red Hat Enterprise Linux/CentOS 7.7 64 bit RPM package: CTF-Disconnected-media-20.0.321-620.rhel7.x86_64.rpm
- Red Hat Enterprise Linux/CentOS 6.10 64 bit RPM package: CTF-Disconnected-media-20.0.321-620.rhel6.x86_64.rpm
b. Back up the old repo file.

For example:
```
   mv /etc/yum.repos.d/CTF-Disconnected-media-19.3.382.repo /etc/yum.repos.d/CTF-Disconnected-media-19.3.382.repo.cn_backup
```
c. Unpack the 20.0 Update 1 disconnected installation package.
```
   rpm -Uvh <package-name>
```
d. Verify your yum configuration files.
```
   yum list httpd
   yum list apr
```
Configure your TeamForge installation repository. This step is to configure TeamForge 20.0 Update 1 installation repository on sites with Internet access.

a. Remove the existing TeamForge repository package.
```
   yum erase collabnet-teamforge-repo-19.3-0.noarch
```
b. Contact the CollabNet Support and download the TeamForge 20.0 Update 1 installation repository package to /tmp.

c. Install the Teamforge 20.0 Update 1 installation repository package.
```
   yum install -y /tmp/collabnet-teamforge-repo-20.0-0.noarch.rpm
```
d. Refresh your repository cache.
```
   yum clean all
```
Install the TeamForge 20.0 Update 1.
```
yum install teamforge
```
The above command installs all the TeamForge updates available in the CollabNet yum repository for TeamForge 20.0.
Check the /opt/collabnet/teamforge/var/scm/gerrit/gitroot directory. If it is empty, remove it manually.
```
rm -rf gitroot
```
Deploy services.
```
teamforge provision
```

Tags for this page: