Head of Infrastructure and DevOps at a manufacturing company with 5,001-10,000 employees
Real User
Jan 13, 2023
The core functionality is most valuable for indexing and metadata of all the artifacts, but within the last year or two, we've been using the Projects feature, which has been very helpful. We can now assign individual admins for different projects and repos so that they can self-manage their own user permissions for their data. My IT DevOps team doesn't have to be the facilitators of that. It's now more of a self-service capability for them.
Senior DevOps Engineer at a computer software company with 1,001-5,000 employees
Real User
Dec 20, 2022
The feature that I like is Permission Targets. If I want to give permission to only deploy the cache, I can give that permission to a set of users. Similarly, if I want to overwrite an artifact with the same name from the same pipeline, I can give permission for that as well to particular users.
The most valuable feature right now is that the tool is invisible. I've set it up so that it works in my build process and my release processes, and it just works. I hardly ever need to go into the UI to check up on things or correct anything. By far, the biggest feature for me is that after setup, it just keeps on working.
JFrog Artifactory is a centralized repository that supports multiple artifact types, providing integration into CI/CD pipelines and authentication systems while ensuring secure access control and high availability.JFrog Artifactory offers universal artifact management with features like versioning, global caching, and real-time federation. Organizations appreciate its scalability and consistent artifact handling, which reduces deployment errors and improves collaboration. While integration...
The core functionality is most valuable for indexing and metadata of all the artifacts, but within the last year or two, we've been using the Projects feature, which has been very helpful. We can now assign individual admins for different projects and repos so that they can self-manage their own user permissions for their data. My IT DevOps team doesn't have to be the facilitators of that. It's now more of a self-service capability for them.
The feature that I like is Permission Targets. If I want to give permission to only deploy the cache, I can give that permission to a set of users. Similarly, if I want to overwrite an artifact with the same name from the same pipeline, I can give permission for that as well to particular users.
The most valuable feature I have found is the JFrog CLI.
HPE was using it for a lot of things, and they certainly had a massive implementation.
The most valuable feature right now is that the tool is invisible. I've set it up so that it works in my build process and my release processes, and it just works. I hardly ever need to go into the UI to check up on things or correct anything. By far, the biggest feature for me is that after setup, it just keeps on working.
The package registries have been helpful. GitLab, our previous solution, wasn't managing that well.