When upgrading the nodes in a CloudBees CD/RO cluster, you must keep the other nodes stopped until the primary node upgrade is complete.
Also, after upgrading from CloudBees CD/RO 10.8 or earlier, delete all
Enter the following command to make the installer file executable:
chmod +x ./CloudBeesFlow-<version>
CloudBeesFlow-<version>file to begin installation. The Welcome to the CloudBees CD/RO Install Wizard screen appears.
Choose one of the following options:
Select Upgrade the existing installation if you want to upgrade your current CloudBees CD/RO installation directory.
Select Perform a clean install if you want to specify a different installation directory for the new version.
During a clean installation, current services remain running until you click Next on the Ready to Install screen. This means the new installation cannot use the same ports and directories as the existing installation. To use the same ports and directories, you must manually stop the existing services. This will free the existing ports and directories.
Click Next to upgrade the existing installation. The Ready to upgrade screen appears.
Review the upgrade settings.
Use the Back button to change your selections if necessary.
Click Next to continue.
The installer displays a status bar to show the progress of the upgrade process. You can also view the
installer.logfile to see progress. The time that it takes to complete this process depends on the size of the database. It may take fifteen minutes or longer to complete. Once this process is complete, the new CloudBees CD/RO version is installed.
Select the Launch a web browser to login to CloudBees CD/RO check box if you want CloudBees CD/RO to open the login screen now.
Click Finish to complete the upgrade.
If a CloudBees CD/RO server is being upgraded, when the installation is complete, the server continue to upgrade the database (if applicable). You cannot log in to the CloudBees CD/RO server until the database upgrade finishes. You can view the upgrade status by using
ectoolfrom a command line:
However, for upgrades involving large databases, the output from
ectool getServerStatusmight remain unchanged for long periods. In this case, you can see more granular database update activity by following the procedure in the KBEC-00086 - Enabling and collecting voluminous JDBC logging KB article to add SQL logging to the
<data_dir>/logs/commander.logfile. You can view recent SQL logging updates to the file by using the Linux
After clicking Finish, you might see a web page similar to the following screen if the upgrade is still in progress: