Fix typos and change some grammatical constructions
This commit is contained in:
@@ -2,9 +2,9 @@
|
||||
title: "Artifactory"
|
||||
ring: trial
|
||||
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.
|
||||
|
||||
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.
|
||||
|
||||
@@ -15,6 +15,6 @@ Artifactory provides a powerful REST-API for managing Artifacts including a powe
|
||||
|
||||
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.
|
||||
* The Composer Integration mirroring github proves to be slower than directly connecting to github.
|
||||
* The Composer Integration mirroring GitHub proves to be slower than directly connecting to GitHub.
|
||||
|
||||
AOE is using the Professional version for a central instance that can be used by different teams. We encourage teams to use Artifactory instead of Jenkins to store and manage build artifacts - and to take care of cleaning up old artifacts automatically.
|
||||
|
||||
Reference in New Issue
Block a user