Need help with other JFrog products?
JFrog Enterprise+
JFrog Mission Control
JFrog Xray
JFrog Distribution
[JFrog Pipelines]
JFrog Bintray
JFrog Access
JFrog CLI
Note | ||
---|---|---|
| ||
From Artifactory version 6.6, you can exclude builds only using the System Export REST API. This is no longer available from the UI. |
Info |
---|
Note: The System Import and Export feature is not available for Artifactory Cloud users. |
To access import and export of your entire system, in the Admin module, select Import & Export | System
Tip | ||
---|---|---|
| ||
From version 5.10, Artifactory maintains all security entities (users, groups, permissions and access tokens) when doing a system import. Previously, these entities would be removed along with existing configurations, repositories and artifacts. |
Target Export Dir | The target directory for the exported files. You may browse your file system to select the directory | |||||
Exclude Content | Export: When set, repository binaries are excluded from the export. Import: When set, binaries and metadata are excluded from the import. Only builds and configuration files are imported. | |||||
Exclude Metadata | When set, repository metadata are excluded from the import/export.
| |||||
Exclude Builds | When set, all builds are excluded from the export | |||||
Create .m2 Compatible Export | When set, includes Maven 2 repository metadata and checksum files as part of the export | |||||
Create a Zip Archive (Slow and CPU Intensive!) | When set, creates and exports to a Zip archive | |||||
Output Verbose Log | When set, lowers the log level to "debug" and redirects the output from the standard log to the import-export log.
|
The source/target of the import/export operations are folders (Zip archives are not recommended) on the Artifactory server itself.
You can use the built-in server-side browsing inside Artifactory to select server-side source/target folders:
Info |
---|
Importing or exporting a large amount of data may be time consuming. During the import/export operation you can browse away from the page and sample the System Logs to monitor progress. |
When performing a system export and subsequent import for an HA cluster, you need to follow the procedure below to ensure that the cluster is able to correctly synchronize its nodes.
Expand | |||||
---|---|---|---|---|---|
| |||||
|
Expand | |||||
---|---|---|---|---|---|
| |||||
|
Once you have completed the import, we recommend verifying that your HA cluster is up and running normally as described in Testing your HA Configuration.
Info |
---|
Note: Importing repositories is supported for all users whereas exporting repositories is only available for non-SaaS users. |
To access import and export of repositories, in the Admin tab, select Import & Export | Repositories
When exporting, you need to specify the following parameters:
Source Local Repository | You can specify a single repository to export, or All Repositories | |||||
Export to Path | The export target directory on your server | |||||
Exclude Metadata | When set, repository metadata are excluded from the export.(Maven 2 metadata is unaffected by this setting) | |||||
Create .m2 Compatible Export | When set, includes Maven 2 repository metadata and checksum files as part of the export | |||||
Output Verbose Log | When set, lowers the log level to "debug" and redirects the output from the standard log to the import-export log.
|
You can import repositories from a server side folder, or by zipping a repository and uploading it to Artifactory.
When importing, you need to specify the following parameters:
Target Local Repository | You can specify a single repository to import, or All Repositories. The repository layout should be different depending on your selection. Please refer to Import Layout | |||||
Server Path for Import | The import source directory on your server | |||||
Exclude Metadata | When set, repository metadata are excluded from the import | |||||
Output Verbose Log | When set, lowers the log level to "debug" and redirects the output from the standard log to the import-export log.
|
Note | ||
---|---|---|
| ||
To work with a Docker repository, it must have its metadata intact. Therefore, when importing to/exporting from a Docker repository make sure that Exclude Metadata is not checked. |
Tip | ||
---|---|---|
| ||
You can take advantage of remote repositories you have already downloaded to your local environment, and import them directly into a local repository. For example, you can take your local Maven repository (usually located under ~/.m2) and upload it into Artifactory so that all the artifacts you have already downloaded are now available on the server. |
An imported repository needs to be formatted using a Maven 2 repository layout.
When importing a single repository, the file structure within the import folder (or zip file) should be as follows:
Code Block |
---|
IMPORT_FOLDER/ZIP_FILE | |--LIB_DIR_1 |
When importing all repositories, the file structure within the import folder should be as follows:
Code Block |
---|
IMPORT_FOLDER/ZIP_FILE | |--REPOSITORY_NAME_DIR_1 | | | |--LIB_DIR_1 |
Info |
---|
When importing all repositories, you need to ensure that the names of the directories representing the repositories in the archive match the names of the target repositories in Artifactory. |