Repository Export
The Repository - Export assets task will export all the content from a selected repository into a directory in your server. The content of this export directory can be imported to another Nexus Repository Manager instance using the Repository - Import external files task.
Available in Nexus Repository Manager Pro only
Configuration
Create a new task of type Repository - Export assets and you will be presented with the configuration options listed below:
A number of these fields are common to all tasks, so we won't go into details here, but the export specific fields are as follows:
Source repository - The repository to export content from. This list will only be populated with repositories of the supported formats (see format list below).
Target directory - The directory to export content into.
The target directory must be writable by the user running Nexus Repository Manager 3. The export history is stored in the target directory to enable incremental exports.
Usage
The task can be configured to run manually or on a schedule fitting your needs. And when the task runs, it generates a .nexus
directory inside of the target directory, that contains some metadata we use for future exports, so that content won't be exported multiple times if the task is run more than once. This will allow you to keep exporting content into this directory, and the next time the export task runs, only the newer content will be exported.
As the export is being processed, every single file that is exported will be logged to a task log (a new task log is created each time a task runs), along with any errors that may have occurred. If an error occurs with any particular asset, we will simply log that fact, then continue on exporting the rest of the content.
Supported Formats
Currently, content can be exported from repositories of any format listed below:
Format | Since |
---|---|
Raw | 3.24.0 |
Maven | 3.24.0 |
npm | 3.25.0 |
NuGet | 3.25.0 |
Docker | 3.26.0 |
PyPI | 3.26.0 |
RubyGems | 3.26.0 |
Yum | 3.26.0 |