Upgrade

Enter the version you want to upgrade to. In addition to version, an optional URL can be provided for an alternative product installation file. This is mostly used internally at Atlassian for testing purposes.

Traditional upgrade process

Weaver will destroy all the current nodes immediately, and create new ones on the new version, by first bringing up one node to run the upgrade tasks, then bringing up the rest.

Zero Downtime (ZDU)/Rolling upgrades

Upgrades can be done with no downtime if you have more than one node in the cluster, are on a ZDU/rolling upgrade compatible version, and have the credentials of an account with the System Administrator permission in the application.

In this case, you can choose whether the existing nodes will be destroyed/replaced or upgraded in-place one by one.

Bitbucket

Currently Bitbucket can only support rolling upgrades (ie no downtime) for minor versions, ie 7.9.0 to 7.9.3. Watch BSERV-7894 for updates on major/feature version rolling upgrade compatibility.

Confluence

As of 7.14, Confluence supports rolling upgrades between minor versions, and to the next major/feature version, ie 7.9.0 to 7.9.1, and 7.14.x to 7.15.x. See Upgrade Confluence without downtime for more information.