Relax directory check on the Upgrade flow of the installer

Problem Definition

In order to migrate Stash/Bitbucket server to a different server, customers need to follow the procedure below:

• Download the Backup/restore client. This is a Java application that has to be run on the same server as where your Stash/Bitbucket server instance is running.
• Backup your current Bitbucket Server using the client you downloaded above
• Restore the file generated in the operation above into the new server (stash-YYYYMMDD-HHMMSS-ID.tar file should be inside the <backup-tool>/backups). Please use the guidelines below:
  • Restoring Bitbucket Server to use a newly created DB

The problem occurs when the restore is completed. If you try to upgrade the current restored BITBUCKET_HOME by using the installer, the validation done by the installer sees the restore as invalid and shows this message:

The home directory structure could not be recognized. Please choose a valid home directory

Cause

The cause for that is that the installer checks for the existence of the following directories to decide whether or not the home directory is OK to upgrade: "caches", "export", "log", "plugins", "shared", "shared/data", "shared/config", "shared/plugins", "tmp"

However, according to What is backed up, our backup client does not backup "caches", for example.

Suggested Solution

Relax the restriction check on the Upgrade workflow to make it match what we backup with the client by default.

Workaround

As a workaround, customers migrating should:

1. Install the binary that is running on the original server pointing to an empty directory, it will start up just like a first installation screen (i.e. it will ask you to enter details of license, etc.)
2. If that's achieved, your installation was successful. Please stop your instance at this point.
3. Copy the content of the restored directory into the empty STASH_HOME of this new installation
4. Restart the newly installed Stash
5. At this stage, an upgrade will be performed. You should be able to see the same content as the old machine on the Stash UI
6. Upgrade your instance to the most recent release only once you got the old installation completely functional