In Artifactory, a repository is a place to organize your artifacts into a cohesive, organized group by application and project.
Artifactory hosts the following repository types:
Local repositories store and manage the artifacts that your organization uploads or creates internally (sometimes referred to as first-party and second-party artifacts). They are ideal for storing the build artifacts, binaries, and other packages that you generate.
Remote repositories serve as a caching proxy for repositories managed at a remote URL, such as a public registry. These repositories contain artifacts that originate outside your local machine, for example, your project's dependencies.
Virtual repositories aggregate an unlimited number of local and remote repositories to create controlled domains for the search and resolution of artifacts.
Federated repositories synchronize their contents with other Federated repositories located at remote sites that are part of the same Federation.
Build Info is all the information collected by the build agent, which includes details about the build. For more information on Build Info, see About Build Info.
Note
Enterprise+ customers with JFrog Distribution can also create and manage Release Bundle repositories, which are used to collect a signed group of artifacts and protect them from changes to ensure consistent distribution to targets, such as JFrog Artifactory Edge nodes.
Manage Repositories
To create and manage repositories, go to Repositories under the Administration module.
Administrators can create repositories for a selected package type and assign them to a particular environment. After defining other basic and advanced settings, as required, they can optionally set up replication with a target repository.
Quick Setup Wizard
You can also use the Quick Setup wizard, which enables you to create repositories for your selected package types in one go. With a couple of simple steps, you can create local, remote, and virtual repositories for each package type of your choosing. For more information, see Quick Repository Setup.
Uploading Non-Conformant Content
Repositories of each package type have built-in logic for parsing metadata, creating index files, and optimizing performance for packages of that specific type. Uploading non-conformant content, such as images, text files, and other resources that are not wrapped in the proper package format can impact indexing and reduce performance. Therefore, it is strongly recommended to upload generic content to a Generic repository.