Overall Satisfaction with JFrog Artifactory
JFrog Artifactory is being used as the single binary repository for our entire enterprise. We store everything from application artifacts to Docker images to NPM, Maven, and Python packages as dependencies in [JFrog] Artifactory. It's a mission-critical component of our CICD pipelines.
- Stores and Manages build artifacts and packages.
- Works as container registry as well.
- Easily manages local and remote repositories along with live replication.
- JFrog Artifactory X-Ray isn't mature enough.
- There should be some built-in backup and restore features.
- Support responsiveness needs to be improved it takes days to get response.
- OSS version has very basic features and enterprise one is costly.
- Artifact, Package and Helm chart repository hosting.
- Container image registry.
- Integration support with build and CI tools.
- So many times it happens at the time of dependency resolution some of the servers are down e.g NPM, Maven central, PiPy in that cause our builds starts failing. By proxying these repositories with JFrog this is never happened again.
- It reduced the additional cost of container image registry and management effort.
- Support of integration with Build, Monitoring, and CI tools resulted in smooth automation and management.
Do you think JFrog Artifactory delivers good value for the price?
Are you happy with JFrog Artifactory's feature set?
Did JFrog Artifactory live up to sales and marketing promises?
I wasn't involved with the selection/purchase process
Did implementation of JFrog Artifactory go as expected?
Would you buy JFrog Artifactory again?