Upgrading from 1.2.5 to 1.2.5u1

1. Export the full system into a zip file using the UI.
2. Install Artifactory 1.2.5u1 into a new clean directory ($ARTIFACTORY_HOME).
3. Extract the artifactory.config.xml from the root of the export zip and change the following:

   http://www.jfrog.org/xsd/artifactory-v1_1_0.xsd
   with:
   http://www.jfrog.org/xsd/artifactory-v1_2_0.xsd

   and,

   http://artifactory.jfrog.org/xsd/1.1.0
   with:
   http://artifactory.jfrog.org/xsd/1.2.0

   and,

   <snapshotVersionBehavior>nonunique</snapshotVersionBehavior>
   with:
   <snapshotVersionBehavior>non-unique</snapshotVersionBehavior>

4. Replace the artifactory.config.xml in the zip with the one you just edited.
5. Restart Artifactory.
6. Re-import all your system from the updated zip file.

   Future versions of Artifactory will handle schema changes automatically, to remove the hassle of having to manually update the config file.

Upgrading from 1.2.2 and from 1.2.5 RCs to 1.2.5

1. Export all your existing repositories (or the full system if using a 1.2.5 RC) using the UI.
2. Install Artifactory 1.2.5 into a new clean directory ($ARTIFACTORY_HOME).
3. Edit $ARTIFACTORY_HOME/etc/artifactory.config.xml to reflect the repositories you have and any virtual repositories you wish to set up.
4. Restart Artifactory.
5. Re-import all your repositories using the UI.

Dealing with Invalid Repository Keys

Version 1.2.5 introduces minor changes to the XML schema used by artifactory.config.xml, thus, the easiest approach is to start with the artifactory.config.xml taken from a newly installed Artifactory and modify it as needed.
The most significant change is that repository keys need to be valid xml IDs. One of the implications of this is that keys cannot start with a number (for example, 3rdparty-releases is now an invalid name and needs to be replaced).
For backward compatibility with old POMs using old repository URLs (containing old invalid keys), you can activate repository mapping by specifying system-properties to Artifactory using the following convention: -Dartifactory.repo.key.subst.<old-invalid-id>=<new-valid-id>

Upgrading from 1.2.1 to 1.2.2

Standalone and Tomcat

The newer version of Artifactory contains again a full installation zip.

To upgrade without using any security settings closely follow these steps:

1. Export all your existing repositories using the UI.
2. Shutdown Artifactory.
3. Remove/move aside the $ARTIFACTORY_HOME/data/jcr folder.
4. Make a copy of your $ARTIFACTORY_HOME/etc/artifactory.config.xml file.
5. Unzip the new verson and copy it over to $ARTIFACTORY_HOME.
6. Replace the exiting $ARTIFACTORY_HOME/etc/artifactory.config.xml with the artifactory.config.xml copy you made earlier.
7. Restart Artifactory.
8. Re-import all your repositories using the UI.

On Unix it is recommenderd to reisntall the artifactoryctl script.

Updating the Deployed WAR file on Tomcat

While Tomcat is down, copy the new $ARTIFACTORY_HOME/webapps/artifactory.war file to Tomcat's webapps folder.

Avoid hot-deploy and make sure to delete the extracted artifactory folder under Tomcats' webapps folder before copying over the war file.

Upgrading from 1.2.0.x to 1.2.1

The newer version of Artifactory contains again the whole installation zip/tgz.
So, when unzipping a new verson, you need to keep the important subfolders of your Artifactory home: