During an upgrade, the installer displays the following error prompt:
CloudBees CD/RO is configured to use the built-in database. The built-in
database on disk has a schema intended for CloudBees CD/RO version
<version>, which is older than that needed by this CloudBees CD/RO
<version> server. CloudBees CD/RO does not support version upgrades of
the built-in database, so the CloudBees CD/RO server cannot start. For
options to resolve this issue, see the "Troubleshooting" chapter of
the "CloudBees CD/RO Installation Guide"
This problem occurs because starting with CloudBees CD/RO version 8.0, CloudBees does not support upgrades from CloudBees CD/RO versions that use HSQLDB. HSQLDB is the built-in (default) database that was replaced by MariaDB in CloudBees CD/RO version 8.3 as the built-in database.
Because the HSQLDB database in CloudBees CD/RO is not upgradeable, to work around this issue, you can either point to a supported database, wipe the database (if you do not need its contents), or migrate the database contents to a database supported by CloudBees CD/RO.
To point to a different CloudBees CD/RO-supported database, modify the
database.properties file to point to that database.
If you do not need the contents of the built-in database, complete the following steps:
Back up the database.
For details, refer to CloudBees CD/RO server backups.
Delete the files and folders whose names match the pattern:
If you do need the contents of the built-in database, complete the following steps:
Back up your
<DATA_DIR>\builtinfolder and your
keystorefiles (or simply back up the entire
Reinstall the prior CloudBees CD/RO version by using the following substeps:
Uninstall the newer instance that is not working.
Install the prior version again, which uses a new built-in database by default.
If you installed the CloudBees Analytics server on the same system, you must use a different
<DATA_DIR>for this CloudBees CD/RO server installation.
CommanderServerservice starts (meaning that the plugins are installed and so on) and you can log into the installed version from substep b, stop the
Back up the new
<DATA_DIR>\conffolders and replace them with the folders that you backed up in step 1.
Restart the new
CommanderServerservice. It should now use the original built-in database containing your data and should function properly.
Do a full export of the database contents.
For details, see CloudBees CD/RO server backups.
Switch to another production-quality database that CloudBees CD/RO supports.
For details, see Configuring CloudBees CD/RO to Use an Alternate Database.
Do a full import of your data to the new database.
For details, see Restoring a CloudBees CD/RO server.
Re-upgrade CloudBees CD/RO.