Artifactory provides you with the features you need to manage your binary repositories, both through an intuitive UI and with an extensive set of APIs.
The Artifactory UI is divided into four main modules:Artifacts, Search, Build and Admin
Configuring different entities such as repositories, software licenses, proxies, mail servers and more
Managing different aspects of system security such as user definitions, groups, permissions, LDAP integration and more
Managing backup and indexing of repositories
Managing import and export of repositories or of the entire system
Accessing system information and scheduling different cleanup operations
To facilitate easy navigation through its UI, Artifactory offers the following set of keyboard shortcuts:
Ctrl/Cmd + Alt + B | Display the Build Browser in the Build module |
Ctrl/Cmd + Alt + R | Display the Artifact Repository Browser in the Artifacts module |
Ctrl/Cmd + Alt + N | Create a new item (where relevant). For example, when viewing the list of local repositories, Ctrl/Cmd + Alt + N will pop up a dialog to create a new one. |
Ctrl/Cmd + Alt + > | Open the Admin module menu. Once in the menu, you can browse through items using the up/down arrow keys or the tab key. |
Ctrl/Cmd + Alt + < | Close the Admin module menu. |
Repository Types in Artifactory
Artifactory hosts three types of repository:
Local repositories are physical, locally-managed repositories into which you can deploy artifacts. Artifacts in a local repository can be accessed directly using the following URL:
http://<host>:<port>/artifactory/<local-repository-name>/<artifact-path>
Artifactory is deployed with a number of pre-configured local repositories which can be used for internal and external releases, snapshots and plugins.
A remote repository serves as a caching proxy for a repository managed at a remote URL (which may itself be another Artifactory remote repository). Artifacts are stored and updated in remote repositories according to various configuration parameters that control the caching and proxying behavior. You can remove artifacts from a remote repository cache but you cannot actually deploy a new artifact into a remote repository.
Artifacts in a remote repository can be accessed directly using the following URL:
http://<host>:<port>/artifactory/<remote-repository-name>/<artifact-path>
This URL will fetch a remote artifact to the cache if it has not yet been stored.
A virtual repository (or "repository group") aggregates several repositories with the same package type under a common URL. The repository is virtual in that you can resolve and retrieve artifacts from it but you cannot deploy artifacts to it.
Local and remote repositories are true physical repositories, while a virtual repository is actually an aggregation of them used to create controlled domains for search and resolution of artifacts.
To configure repositories, in the Admin module, select Repositories.
Repositories can be created, deleted, edited, ordered and aggregated.
When creating any repository, you must specify its package type; this is a fundamental characteristic of the repository and can not be changed later. Once the repository type is set, Artifactory will index artifacts and calculate the corresponding metadata for every package uploaded which optimizes performance when resolving artifacts. Note that virtual repositories can only include repositories of the same type.
You may define a repository as Generic in which case it has no particular type, and you may upload packages of any type. Generic repositories do not maintain separate package indexes. For using a client associated with a specific package type (e.g. yum, gem) you should create a matching repository.
You can set the order in which repositories of each type (local, remote and virtual) are searched and resolved by simply ordering them accordingly within the corresponding section of the Configure Repositories page. To set the order you need to add the repositories to the list of selected repositories in the order in which they should be searched to resolve artifacts.
The order in which repositories are searched is also affected by additional factors such as security privileges, include/exclude patterns and policies for handling snapshots and releases.