Upgrading Artifactory to Version 2.6.x
(from 1.3.0-RC, 2.0.x-2.5.x)
Storage Type Changes: if you also wish to change the underlying storage type used by Artifactory, please read the following instructions instead.
The instructions below assume the upgraded Artifactory will use the existing storage type.
When Running the Artifactory WAR in a Servlet Container
- Unzip the Artifactory distribution archive.
- Replace the previously deployed
artifactory.war file with the archive's webapps/artifactory.war file.
On servlet containers such as Tomcat it is also necessary to remove the exploded artifactory webapp directory.
 | Starting with version 2.1.1 Artifactory's only distribution format is a single zip archive (artifactory-x.y.z.zip) that also contains the artifactory.war file in the webapps directory. |
When Running Standalone Artifactory
- Unzip the Artifactory distribution.
Replace the following files and folders in you current $ARTIFACTORY_HOMEwith the same files from the new version:
| The misc folder contains configuration files for specialized environments such as a standalone Tomcat server or Websphere. Although these files are not required for runtime, it is recommended to replace this folder as well. |
- Delete Jetty's work folder (
$ARTIFACTORY_HOME/work) before starting up Artifactory.
When Running the RPM Installation
- Log in as root (or use
'sudo su -'). - Execute
'rpm -U artifactory-x.y.z.rpm'
| When upgrading from Artifactory prior to 2.6.0, please make sure to manually stop the current Artifactory service before running the upgrade, and verify the process has exited. |
Upgrading From Legacy Versions
If you would like to upgrade from Artifactory versions below 1.3.0-RC, you will need to upgrade Artifactory to version 2.0.x first. Please follow these steps.
 | When upgrading from 2.1.x or 2.0.x
The Artifactory upgrade process is fully automated. However, the automatic upgrade to this version will likely run longer than you are used to:
As part of the performance improvements done for this version we had to upgrade the way artifact metadata is stored and indexed inside Artifactory. The result is much faster searches and significantly improved performance of the whole system under load.
However, since repository metadata and index need to be rebuilt, the upgrade process may take some time to complete (this time varies depending on your CPU and disk speed).
Artifactory will not serve incoming requests until the automatic upgrade process completes, so you may want to schedule the upgrade accordingly. You can follow the progress of the upgrade process in the the artifactory log file. Preserving Build Information
Please also note that using the upgrade process is the only way to move deployed build-information forward. You cannot import an export of 2.1.x with BuildInfo data into 2.3.x. This is a result of a bug that has already been resolved. |
Upgrading Artifactory