Skip to content

Commit

Permalink
Add missing line-break to Artifactory article
Browse files Browse the repository at this point in the history
  • Loading branch information
mathiasschopmans committed Apr 4, 2017
1 parent 9ae5a8f commit 1d12280
Showing 1 changed file with 6 additions and 0 deletions.
6 changes: 6 additions & 0 deletions radar/2017-03-01/artifactory.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,11 +6,17 @@ quadrant: platforms-and-aoe-services
---

JFrog [Artifactory](https://www.jfrog.com/open-source/) is a software tool, which, in the end, manages and stores (binary) artifacts.

In addition to storage, it provides a managing interface, which also allows to store build information, properties as well as dependencies per artifact which are organized within repositories. A fine grained security system enables easy management of which artifacts are available to whom.

The artifacts are exposed via an HTTP(S)-Url Artifactory, which can generate package-manager compatible manifests for the repositories. AOE utilizes Artifactory to serve Maven, Apt, Npm, Composer and Docker Repositories.

In addition to storing own assets, Artifactory is able to proxy remote Repository for and cache resolved artifacts locally.

This results in an increased build performance and decouples builds from external service dependencies and ensures builds still work even if they utilize outdated dependencies that might not be publicly available anymore.

Artifactory provides a powerful REST-API for managing Artifacts including a powerful search AQL. It is utilized to provide complex release processes based on QA-Attributes on an artifact level.

Artifactory at AOE currently comes with some problems, too:

- Cleanup in Artifactory has to be done manually. Therefore, if every build is pushed to Artifactory it currently pollutes disk space since old or unused versions are never removed.
Expand Down

0 comments on commit 1d12280

Please sign in to comment.