Upgrade Review Board

Back up the Review Board Data Directory

The default Review Board data directory has been changed from /opt/collabnet/reviewboard/data to /opt/collabnet/teamforge/var/reviewboard/data in TeamForge 17.4.

Are You Upgrading from TeamForge 17.1 or Earlier to TeamForge 17.4 or Later?

If you are upgrading from TeamForge 17.1 or earlier to TeamForge 17.4 or later, regardless of whether you upgrade Review Board on the same or new hardware, you must back up your Review Board data directory from /opt/collabnet/reviewboard/data and restore it to /opt/collabnet/teamforge/var/reviewboard/data.

1. Back up the Review Board data directory.

   cd /opt/collabnet
   tar -zcvf /tmp/reviewboard_data.tgz reviewboard
   

2. Copy the /tmp/reviewboard_data.tgz file to the /tmp directory of the new server if you are upgrading Review Board on a new hardware.

Are You Upgrading from TeamForge 17.4 to TeamForge 17.8 or Later?

1. Back up the Review Board data directory.

   cd /opt/collabnet/teamforge/var
   tar -zcvf /tmp/reviewboard_data.tgz reviewboard
   

   Tip: If you are upgrading from TeamForge 17.4 (or later), the /opt/collabnet/teamforge/var directory would have been backed up already as part of your TeamForge upgrade process, in which case you can skip backing up the /opt/collabnet/teamforge/var directory again.
2. Copy the /tmp/reviewboard_data.tgz file to the /tmp directory of the new server.

Upgrade Review Board

1. Make sure that reviewboard, reviewboard-database and reviewboard-adapter identifiers have been added to the SERVICES token of the TeamForge Application Server (server-01).

   server-01:SERVICES=ctfcore ctfcore-database mail search codesearch etl ctfcore-datamart subversion cvs gerrit gerrit-database binary binary-database reviewboard reviewboard-database reviewboard-adapter cliserver
   

   It is assumed that the Review Board is running on the TeamForge Application Server. In case you have a separate Review Board Server, add the reviewboard and reviewboard-database identifiers to the Review Board server’s SERVICES token.
2. Configure the TeamForge installation repository.

   TeamForge Installation Repository Configuration for Sites with Internet Access

   1. Contact the CollabNet Support and download the TeamForge 19.1 installation repository package to /tmp.
   2. Install the repository package.

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

   3. Refresh your repository cache.

      yum clean all
      

   TeamForge Installation Repository Configuration for Sites without Internet Access

   1. Contact the CollabNet Support to get the auxiliary installer package for TeamForge 19.1 disconnected installation and save it in /tmp.
      • RHEL/CentOS 6.10 64 bit: CTF-Disconnected-media-19.1.272-783.rhel6.x86_64.rpm
      • RHEL/CentOS 7.6 64 bit: CTF-Disconnected-media-19.1.272-783.rhel7.x86_64.rpm
      • In addition to the above CentOS 7.6 64 bit RPM package, you must get the following CentOS 7.6 compatibility RPM, which is required for TeamForge 19.1 disconnected media installation on CentOS 7.6 profile: compat-ctf-dc-media-1.2-1.el7.noarch.rpm.
   2. Unpack the disconnected installation package.

      rpm -Uvh <package-name>
      

   3. Unpack the compat-ctf-dc-media-1.2-1.el7.noarch.rpm package if you are installing TeamForge 19.1 on CentOS 7.6.

      rpm -ivh compat-ctf-dc-media-1.2-1.el7.noarch.rpm
      

   4. If you are installing TeamForge 19.1 on RHEL/CentOS 6.10, contact the CollabNet Support to get the python-modules-sources-el6.zip file and unzip it to /opt/collabnet/teamforge/service/reviewboard/resources/SOURCES/python-modules-sources.

         unzip python-modules-sources-el6.zip -d /opt/collabnet/teamforge/service/reviewboard/resources/SOURCES/python-modules-sources
      

      If you are installing TeamForge 19.1 on RHEL/CentOS 7.6, contact the CollabNet Support to get the python-modules-sources-el7.zip file and unzip it to /opt/collabnet/teamforge/service/reviewboard/resources/SOURCES/python-modules-sources.

      unzip python-modules-sources-el7.zip -d /opt/collabnet/teamforge/service/reviewboard/resources/SOURCES/python-modules-sources
      

   5. If not mounted already, mount the RHEL/CentOS installation DVD.

      The DVD contains the necessary software and utilities required for installing TeamForge without internet access. In the following commands, replace “cdrom” with the identifier for your server’s CD/DVD drive, if necessary.

      cd /media/
      mkdir cdrom
      mount /dev/cdrom ./cdrom/
      

      If there are any spaces in the automount, unmount it first and mount it as a filepath, with no spaces.

   6. Create a yum configuration file that points to the RHEL/CentOS installation DVD.

      vi /etc/yum.repos.d/cdrom.repo
      

      Here’s a sample yum configuration file.

      [RHEL-CDROM]
      name=RHEL CDRom 			
      baseurl=file:///media/cdrom/Server/
      gpgfile=file:///media/cdrom/RPM-GPG-KEY-redhat-release 
      enabled=1
      gpgcheck=0
      

   7. Verify your yum configuration files.

      yum list httpd
      yum list apr
      

   Tip: If you have TeamForge installed, you would have the installation repository already configured.
3. Upgrade Review Board.

   yum install teamforge
   

4. Do this on sites without internet access.
   1. Contact the CollabNet Support and get the python-modules-sources.zip file.
   2. Unzip the python-modules-sources.zip file to /opt/collabnet/teamforge/service/reviewboard/resources/SOURCES/python-modules-sources.

      unzip python-modules-sources.zip -d /opt/collabnet/teamforge/service/reviewboard/resources/SOURCES/python-modules-sources
      

5. Provision services.

   teamforge provision
   

6. Restore the Review Board data.

   The default Review Board data directory has been changed from /opt/collabnet/reviewboard/data to /opt/collabnet/teamforge/var/reviewboard/data in TeamForge 17.4. If you are upgrading from TeamForge 17.1 or earlier to TeamForge 17.4 or later, regardless of whether you upgrade Review Board on the same or new hardware, you must back up your Review Board data directory from /opt/collabnet/reviewboard/data and restore it to /opt/collabnet/teamforge/var/reviewboard/data.
   
   If you are upgrading from TeamForge 17.4 (or later), the /opt/collabnet/teamforge/var directory would have been restored already as part of your TeamForge upgrade process, in which case you can skip restoring the /opt/collabnet/teamforge/var directory again.
   
   If you are upgrading on a new hardware, ensure that you have already copied the backup of the Review Board data directory to the /tmp directory of the new server.

   cd /opt/collabnet/teamforge/var/
   tar -zxvf /tmp/reviewboard_data.tgz
   

7. If SCM is installed on a separate box, run the following script to authenticate a scmviewer user against a TeamForge Subversion repository for creating a new review request.

    python ./svn-auth.py --repo-path=https://<scm_domain>/svn/repos/<repo_dir_name>
   

Post Upgrade Tasks

• Add Review Board to Projects
• Users are not getting email notifications for review requests and reviews. What should I do?

Bootstrap Review Board Post Install or Upgrade

Use the following instructions if you want to bootstrap Review Board (drop Review Board database tables and recreate them again) for some reason post installation or upgrade.

1. Log on to the server that hosts the Review Board.
2. Select My Workspace > Admin.
3. Select Projects > Integrated Apps.
4. Select Review Board and click Delete.
5. Stop TeamForge.

   teamforge stop
   

6. Start the TeamForge database services.

   teamforge start -s postgres
   

7. Bootstrap the Review Board database.

   teamforge bootstrap -s reviewboard-database-postgres
   

8. Bootstrap the Review Board.

   teamforge bootstrap -s reviewboard
   

9. Start TeamForge.

   teamforge start
   

[]: