Upsource

Upgrading your Upsource installation

Upsource uses the major.minor.patch version numbering scheme. Upgrade procedures vary significantly depending on the version increment (1.0 to 2.0 vs 1.0 to 1.0.1). Both procedures are outlined below.

Note: All commands listed below are Windows commands. If you’re working on a Linux or Mac OS X server, simply replace .bat with .sh.

Major or minor version upgrade

Follow this instruction when upgrading to a major or minor release version, e.g. from 1.0.1 to 2.0 or from 2.0 to 2.5

  1. Create a backup while your existing Upsource installation is running.

  2. Stop Upsource: <upsource_home>\bin\upsource.bat stop

  3. Use your operating system’s tools to make sure that all Java processes launched by Upsource are no longer running (on Windows, you can use Process Explorer.
    • If there are no Upsource-related Java processes outstanding, proceed to step 4.
    • If there are Upsource-related Java processes still running:
      1. (Optional, Windows only) Please consider taking thread dumps from those processes using the jstack tool (on Windows, it’s available under <upsource_home>/internal/java/windows-amd64/bin) and provide the thread dumps to JetBrains for investigation.
      2. Kill the outstanding process trees.

  4. If your <upsource_home> directory name is not build-specific, rename <upsource_home> to Upsource.old (you can use another name).

  5. Unpack the zip archive with a new Upsource build.

    Note: the unzipped installation should not be placed inside an old <upsource_home> directory that contains old files.

  6. Copy data and conf folder from the Upsource.old/backup directory to the new <upsource_home>.

    Note: data and conf folders contain hidden files. Use recursive copying cp -r in Linux to avoid data loss. Before copying data and conf folders to the new installation, the existing data and conf folder in that installation should be deleted to prevent data corruption.

  7. Start Upsource: <upsource_home>\bin\upsource.bat start

Patch version upgrade

Follow this instruction when upgrading to a patch update, e.g. from 2.0.1 to 2.0.3 or from 2.5 to 2.5.2

  1. Stop Upsource: <upsource_home>\bin\upsource.bat stop

  2. Use your operating system’s tools to make sure that all Java processes launched by Upsource are no longer running (on Windows, you can use Process Explorer.
    • If there are no Upsource-related Java processes outstanding, proceed to step 3.
    • If there are Upsource-related Java processes still running:
      1. (Optional, Windows only) Please consider taking thread dumps from those processes using the jstack tool (on Windows, it’s available under <upsource_home>/internal/java/windows-amd64/bin) and provide the thread dumps to JetBrains for investigation.
      2. Kill the outstanding process trees.

  3. If your <upsource_home> directory name is not build-specific, rename <upsource_home> to Upsource.old (you can use another name).

  4. Unpack the zip archive with a new Upsource build.

    Note: the unzipped installation should not be placed inside an old <upsource_home> directory that contains old files.

  5. Copy data and conf folder from the old installation to the new one.

    Note: data and conf folders contain hidden files. Use recursive copying cp -r in Linux to avoid data loss. Before copying data and conf folders to the new installation, the existing data and conf folder in that installation should be deleted to prevent data corruption.

  6. Start Upsource: <upsource_home>\bin\upsource.bat start