Apply TeamForge 17.1 Update 2

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

Note:
  • In a distributed setup, apply TeamForge 17.1 Update 2 on all the servers running TeamForge services. While you can follow these steps to update your TeamForge servers, some of the steps such as stopping the CLI add-on and running the post-install.py are required only on the TeamForge Application Server.

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

Important: You must log in as a root user to apply TeamForge 17.1 Update 2.
  1. Stop the TeamForge CLI add-on (This step is required only for TeamForge Application server).
    • service teamforge_cli_server stop
  2. Stop TeamForge.
    • setenforce 0
    • /opt/collabnet/teamforge/bin/teamforge stop
    Note: Stop TeamForge on all the servers in a distributed setup.
  3. Skip this step if your site has internet access. This step is to configure TeamForge 17.1 Update 2 installation repository on sites without Internet access.
    1. Contact the CollabNet Support to get the auxiliary installer package for TeamForge 17.1 Update 2 disconnected installation and save it in /tmp.
      • Red Hat Enterprise Linux/CentOS 7.3 64 bit RPM package: CTF-Disconnected-media-17.1.556-48.rhel7.x86_64.rpm
      • Red Hat Enterprise Linux/CentOS 6.x 64 bit RPM package: CTF-Disconnected-media-17.1.556-48.rhel6.x86_64.rpm
    2. Back up the old repo file.
      For example:
      • mv /etc/yum.repos.d/CTF-Disconnected-media-17.1.547.repo /etc/yum.repos.d/CTF-Disconnected-media-17.1.547.repo.cn_backup
    3. Unpack the 17.1 Update 2 disconnected installation package.
      • rpm -Uvh <package-name>
    4. Verify your yum configuration files.
      • yum list httpd
      • yum list apr
  4. Configure your TeamForge installation repository. This step is to configure TeamForge 17.1 Update 2 installation repository on sites with Internet access.
    1. Remove the existing TeamForge repository package.
      • yum erase collabnet-teamforge-repo-17.1-1.noarch
    2. Contact the CollabNet Support and download the TeamForge 17.1 Update 2 installation repository package to /tmp.
    3. Install the TeamForge 17.1 Update 2 installation repository package.
      • yum install -y /tmp/collabnet-teamforge-repo-17.1-1.noarch.rpm
    4. Refresh your repository cache.
      • yum clean all
  5. Install the TeamForge 17.1 Update 2.
    • yum install teamforge

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

    Run the following command to install the Binary application packages.
    • yum install cn-binary
  6. Deploy services.
    • /opt/collabnet/teamforge/bin/teamforge provision
  7. Run the post-install.py script (This step is required only for TeamForge Application server).
    • /opt/collabnet/teamforge/runtime/scripts/post-install.py
  8. Restart TeamForge.
    • setenforce 1
    • /opt/collabnet/teamforge/bin/teamforge restart