Virtual Repositories

Basic Settings

The following are fully described in theCommon Settingspage.

• Package Type
• Repository Key
• Repository Layout
• Public Description

• Internal Description

• Includes and Excludes Pattern

In addition, in theRepositoriessection of theBasicsettings screen youselect theAvailable Repositoriesyou want to include in the new virtual repository and move them to theSelected Repositorieslist.

This list can be re-ordered by dragging and dropping within theSelected Repositorieslist.

TheIncluded Repositoriessection displays the effective list of actual repositories included in this virtual repository. If any of the available repositories you have selected are themselves virtual repositories, then theIncluded Repositoriessection will display the local and remote repositories included within them. TheIncluded Repositorylist is automatically updated in case any of the nested virtual repositories change.

Nesting

在Artifactory和fac嵌套是一个独特的特性ilitates more flexibility in using virtual repositories.

Using Includes and Excludes Patterns

The ability to define andIncludes Patternand anExcludes Patternfor virtual repositories (especially when nesting is used) provides a powerful tool you can use to manage artifact requests in your organization.

For example, your organization may have its own artifacts which are hosted both internally in a local repository, but also in a remote repository. For optimal performance, you would want these artifacts to be accessed from the local repository rather than from the remote one. To enforce this policy, you can define a virtual repository called "remote-repos" which includes the full set of remote repositories accessed by your organization, and then specify an Excludes Pattern with your organization's groupID. in this way, any attempt to access your internal artifact from a remote repository would be rejected.

Consider another example in which you wish to define a virtual repository for your developers, however you wish to keep certain artifacts hidden from them. This could be achieved by defining anExcludes Patternbased on groupId, source or version.

Deploying to a Virtual Repository

From version 4.2, Artifactory supports deploying artifacts to a virtual repository. For example you can now usedocker push, npm publish, NuGet push, gem pushArtifactory's REST API and more to deploy packages to a virtual repository.

For more details, please refer toDeploying Artifacts.

Advanced Settings

Maven, Gradle, Ivy and SBT Repositories

In addition to the above checkbox, these repository types offer the followingAdvancedsettings:

 or 

Pre-defined Repositories

Artifactory comes with a set of pre-defined virtual repositories, which reflect binary management best practices as follows.