Skip to end of metadata
Go to start of metadata
Table of Contents

Note: This space is for Artifactory 2.0.
Take me to the latest version!

Upgrading Artifactory to Version 2.0.8

(from 1.3.0-RC1, 1.3.0-RC2 & 2.0.0 to 2.0.7)

When Running the Artifactory WAR Inside a Servlet Container

Simply replace the artifactory.war file. If you are running on Tomcat make sure to also remove the exploded artifactory webapp directory.

When Running Standalone Artifactory

  1. Unzip the 2.0.8 distribution and do one of the following:
    • Link/copy your $OLD_ARTIFACTORY_HOME/data and $OLD_ARTIFACTORY_HOME/etc under the new $ARTIFACTORY_HOME,
      - Or -
    • Replace the following files and folders in you current $ARTIFACTORY_HOME with the same files from the new version:
      clilib/ (/bin/clilib, in 1.3.0-RCs)
  2. Delete Jetty's work folder ($ARTIFACTORY_HOME/work) before starting up Artifactory.

If Running with MySQL (Either as Standalone or WAR)

If running with MySQL (or any database other than the built-in one), open the file $ARTIFACTORY_HOME/etc/repo/mysql/repo.xml and replace the line:

<DataStore class="">

with -

<DataStore class="org.artifactory.jcr.jackrabbit.ArtifactoryDbDataStoreImpl">

Upgrading to 2.0.0 from 1.3.0-RC1 or 1.3.0-RC2

Simply replace the artifactory.war file. If you are running on Tomcat make sure to also remove the exploded artifactory webapp directory.

Upgrading from 1.2.2-rc0 through 1.3.0-beta-6.1

This section covers upgrading from the following versions:

  1.2.2-rc0    1.2.2-rc1    1.2.2-rc2    1.2.2
  1.2.5-rc0    1.2.5-rc1    1.2.5-rc2    1.2.5-rc3    1.2.5-rc4    1.2.5-rc5    1.2.5-rc6      1.2.5 1.2.5u1
  1.3.0-beta-1 1.3.0-beta-2 1.3.0-beta-3 1.3.0-beta-4 1.3.0-beta-5 1.3.0-beta-6 1.3.0-beta-6.1

Upgrading Artifactory from older version can be done in two ways:

  1. From the UI
  2. By using the artadmin command line tool

Upgrading Using the Web UI

Upgrading from the UI is supported only when upgrading from version 1.3.0-x.

  1. From your old Artifactory installation run Full System Export and save the export to a destination directory.
  2. Perform a new clean server installation of the new Artifactory (it should not contain repository data or your customized version of the Artifactory configuration xml file).
  3. Install the new Artifactory version, go to Admin/Export&Import/System/Import System, select your previous export target directory and let the import run. That's it!

Upgrading Using the artadmin Tool

While upgrading from the web UI is easy and straightforward, sometimes the upgrade process can take a long time, especially with very large repositories. In such cases the original web request may time out and the upgrade progress will proceed in the background.
Therefore, if you wish to monitor the progress of the upgrade process in the most reliable way and gain access to more advanced dump options, it is recommended to use the artadmin command-line tool.
Here are step-by-step instructions:

  1. Stop your old Artifactory.
  2. Execute the artadmin dump command on the old $ARTIFACTORY_HOME or on a copy of it (recommended):
    artadmin dump $ARTIFACTORY_HOME
    This will generate a dumpExport folder under the current execution directory with the old repository data in a format suitable for importing into a current Artifactory.
    NOTE: By default, caches (e.g. repo1) are not exported. To export caches add the --caches parameter.
  3. Perform a new clean server installation of the new Artifactory (It should not contain repository data or your customized version of the Artifactory configuration xml file).
  4. Start the new Artifactory.
  5. Import the dumpExport folder into Artifactory, either from the UI, as explained in the previous section or by running:
    artadmin import dumpExport --username admin --password password
    The artadmin output will display the progress of the import. NOTE: If the artadmin process is killed, the import will still run in Artifactory.

Important Information

Please read this carefully before installing or upgrading:

  1. If you have used a previous version of Artifactory it is highly recommended to:
    1. Use a fresh version of Artifactory from the distribution archive and not try to patch the previous installation.
    2. Clear your browser's cache before using the new version.
  2. The default Artifactory user for the standalone installation has been changed to artifactory (instead of jetty). You may need to update the provided install script or your file system permissions accordingly.

Important information about the import process

During the import binary artifacts are copied over into a working copy and are imported into Artifactory by a background thread. This speeds up the import process dramatically and makes Artifactory ready for serving requests as soon as possible. The background import process will take some time to completes, depending on the size of your repository. During this time Artifactory might perform more slowly than usual (it will still serve any artifact immediately, though). The Artifactory log should provide visible information about the progress of this process.

Repeating the upgrade process

Should you wish to repeat the upgrade process from scratch, make sure to remove the $ARTIFACTORY_HOME/data folder from your new Artifactory installation before doing so.

The complete release notes from JIRA for older versions and beta releases are available here:


  • No labels

1 Comment

  1. It would appear that there is a bug in artadmin from 2.0.6 which results in my local hard drive's /tmp folder filling up during the export of a large repo.  artadmin does not honour the TMPDIR environment variable so the only way I haev of exporting the repo seems to be to keep an eye on /tmp and remove the temp files when it starts getting close to full.  If not I get a lot of messages that say the program failed to export a long list of files.

    I also believe that the fact that artadmin is leaving temp files in the folder is a bug - either it is dumping the whole repo to the tmp folder before moving it to the dump folder or it is not removing the temp files once they are finished with (it does so at the end of the run, which is too late for my purposes).

    I have a 40GB repo and 2.5GB /tmp folder, which is adequate for all normal use onthis machine.

    Actually - having spent a while watching the tmp folder artadmin is cleaning up every now and then - the trouble is it seems it's not triggered when the /tmp partition is nearly full though.  Perhaps it would help if a) you triggered a clean up when writing a new file failed or you detected the /tmp folder nearly full? b) allowed the application to use TMPDIR environment variable to find a location where it can place temp files?