We are pleased to announce the availability of Artifactory 1.3.0-beta-6.
Major Features and Changes in this Release
- Artifactory is now fully configurable via the newly designed user interface!
- Support for running Artifactory with MySql for greater scalability, performance and tools support.
- Support for running Artifactory under Websphere.
- Install script for automatic set up under a dedicated Tomcat instance.
- Ability to remove deployed versions with all their sub-artifacts in one go.
- Dynamic log tailing from the UI.
- Global offline flag for disconnected environments.
- Out of the box support for running standalone Artifactory as a Windows service (in additional to the existing Unix service installer).
artadminCLI tool for all administrative tasks.
- Greatly improved backup and restore speed.
- Many internal performance and concurrency improvements.
- The usual bug fixes.
Artifactory is available for immediate download from here.
Major Features and Changes in release 1.3.0-beta-5
- In place incremental backup.
- Performance improvements around security authentication and authorization.
- Fixed a UI bug with remote repositories cache access control setup.
Major Features and Changes in release 1.3.0-beta-4
- Improved LDAP Support - support for multiple DNs, for non-anonymous binding against MS Active Directory and for sub-tree searches.
- Fixed a critical issue with deployment using the lightweight HTTP wagon (RTFACT-629).
- UI and performance improvements and the usual bug fixes.
Major Features and Changes in release 1.3.0-beta-3
- Group support with an intuitive powerful UI for groups management.
- Improved permissions control for including/excluding specific repository paths (e.g. disallow certain users/groups from downloading sources). Simple management - no regexp gurus required.
- Support for delete permission and for preventing users from overriding exiting artifacts.
- Revised repository tree browsing using tabs and effective permissions per item view.
- Improved import speed by committing binary imports asynchronously.
- Improved #upgrade procedure.
- Better transaction management using Spring Modules for JCR.
- Even faster in-place incremental backup.
- Low-level admin-only direct WebDAV access to the underlying jackrabbit repository (use: http://localhost:8081/artifactory/jcr/default/ to connect).
- The usual bug fixes, stability and speed improvements.
The complete release notes from Jira are available here:
Artifactory 1.3.0-beta-6 is available for immediate download here.
The Artifactory Team
Important Notes Before You Install
Please read this carefully before installing or upgrading:
- If you are running Artifactory under JDK 1.6 you MUST use JDK 1.6u4 and above due to incompatibilities with older JAXB versions embedded in previous JDK 1.6 releases. JDK 1.5 users are not affected by this.
- If you have used a previous version of Artifactory it is highly recommended to:
- Use a fresh version of Artifactory from the distribution and not try to patch the previous installation.
- Clear your browser's cache before using this version.
- The default Artifactory user for the standalone installation has been changed to
jetty). You might have to update the provided install script or your file system permissions accordingly.
- Artifactory now includes a convenience method for specifying system properties. Instead of having to configure properties in the runtime configuration of the hosting container, you can now edit the
$ARTIFACTORY_HOME/etc/artifactory.propertiesfile and restart the container. As this affects the whole container VM it is recommended to use this feature for specifying Artifactory related properties only (such as repository ids substitution, etc.).
- Please note that not all documentation has been updated yet to reflect the latest changes in this beta release.
Below is important information that will make it into the final Artifactory 1.3.0 documentation.
Please refer to the Installing section of the current user guide, which still applies.
Upgrading from 1.2.2-rc0 through 1.3.0-beta-5
To upgrade from older versions you first need to dump the data from you old Artifactory into a 1.3 compatible format and then import it to the new Artifactory.
We expect that with 1.3.0 and above upgrading can be done directly on an existing repository without the need to export it first.
Dumping the old version
Since Artifactory 1.3.0-beta-5, JFrog merged the
artdump tool with the main CLI administration tool:
artadmin - creating the CLI "
artadmin tool can be found inside the
artifactory-cli-1.3.x.zip archive, downloadable from here.
Important Information for Running the Dump
- By default, cached repositories (e.g. repo1) are not exported. To export cached repositories pass the
- You should shut down the old Artifactory before executing the export.
- It is recommended to work on a copy of the old
$ARTIFACTORY_HOMEfolder (even though the export should be a read only process).
- If you do not specify a destination folder with
--destoption, the dump command will create a
tmpExportfolder under the current execution directory, where it will export all the data from your old Artifactory.
Step by Step Instructions
Here are step by step instructions for running the full upgrade process:
- Stop the old Artifactory.
- Optional: Copy the
$ARTIFACTORY_HOMEfolder to a new location.
- If you created a copy and wish the old Artifactory to keep serving requests while performing the export, you can start it now.
- Execute the
#artadmin dumpcommand on the old
$ARTIFACTORY_HOMEor on a copy of it, by running
artadmin dump $ARTIFACTORY_HOME(This will generate a
tmpExportfolder if you did not specify a destination folder with
- Perform a new clean server installation of Artifactory 1.3. It should not contain repository data or your customized version of the Artifactory configuration xml file.
- Start Artifactory 1.3. Note: If in step 3 you chose to restart your old Artifactory and you installed the Artifactory 1.3 on the same machine, you will need to alter the listening port number inside
$ARTIFACTORY_HOME/etc/jetty.xml. It is also highly recommended to use a different port in order to perform the upgrade on a "silent" instance that is not being hit by user requests in parallel.
- The import can be done in 2 ways:
- Import with the
artadmincommand line (highly recommended):
--username username --password password.
artadminoutput will display the progress of the import. NOTE: If the
artadminprocess is killed, the import will still run in Artifactory.
- Import via the Web UI:
- Logon with admin/password credentials, click the "Admin" tab and choose "System" from the "Import & Export" sub-menu on the left.
- Enter the export directory into the "System zip file or directory" field in the "Import System" field-set and click the "Import" button.
- The import will run and may take some time to complete (depending on the size of your database).
- Import with the
- Once the import process completes successfully you can switch to using Artifactory 1.3. You can go back to use the old port number (if you changed it in step 6).
Important information about the import process
During the import binary artifacts are copied over into a working copy and are imported into Arifactory in 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, but it will still serve any artifact immediately. The log does 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/datafolder from your new Artifactory installation before doing so.
artadmin dump command line usage:
artadmin import command line usage:
Options for the import process
- When used with the
--symlinksoption, the import process can perform much faster (usually by a factor of 3-5). Note that when using this option your imported path effectively becomes an integral part of Artifactory and you should not move/remove it until the background import process has completed. This is indicated by the log message:
Working copy commit done (0 files).
- When using external database (like MySql) it is recommended to deactivate the working copy mechanism. To do this, use the