My main use case for JFrog Artifactory is that we have been using it to manage binaries, which makes it flexible for diverse development. One of the strongest aspects of JFrog Artifactory is its seamless integration with CI/CD pipelines, allowing version control and artifact storage. A specific example of how I use JFrog Artifactory with my CI/CD is that it plays a critical role in improving reproducibility, dependency management, and deployment consistency. My scenario includes storing and building artifacts, managing Docker images, handling dependency caching, and enforcing version control across environments. The main use case and how we are using JFrog Artifactory was multi-package repository support, as we are using it in CI/CD integration and repository replication, access control management, and artifact version tracking, along with Docker registry capabilities.
I have been using JFrog Artifactory for the past three years. We primarily use JFrog Artifactory for storing our Docker images, packages, artifacts, and other files that we use in our applications on a day-to-day basis. In a CI/CD pipeline, there are several workflows and steps where you bundle your code as an image or as an artifact so that you can use it for running the image in containers using Kubernetes. In those stages of the CI/CD pipeline, we generally build the image using Docker. After building the image, we need to store it for future usage. For storing the images that we build using those CI/CD pipelines, we use JFrog Artifactory in our current environment.
JFrog Artifactory is designed for software management. We used it for storing all assets and packages that were downloaded from external package systems, making them available for our development teams to use in their builds. It primarily supported a fail-fast approach, where vulnerabilities were identified ahead of time, enabling us to alert our development team to use the latest packages without those vulnerabilities. JFrog Artifactory proved very helpful in supporting a variety of package types for different projects.
The main use case was to store the artifacts, store the binaries, basically. And then we used it as a container registry as well. One of my tasks was to get X-ray running. I got the product running and tested it, but users never really started using it. So, from the user perspective, I don't really know how much they used X-ray. What I can say about X-ray is that it did what Artifactory advertised. So, from that point of view, in my opinion, it worked fine, but we never really got to use it too deeply. We never got enough requests from our customers, the developers, or the security management team to implement some checks or block downloads from Artifactory, even when the software is too old or has some vulnerabilities. That was a disappointment for me because I worked on the installation and management of X-ray for a couple of months. But that's not something that X-ray is responsible for.
Head of Infrastructure and DevOps at a manufacturing company with 5,001-10,000 employees
Real User
Jan 13, 2023
We use Artifactory for all of our software development. We're an electric car company, and we're headquartered in China, but we've got an R&D software development office in San Jose. All of our software development teams use Artifactory for storing all their artifacts, binaries, and things like that for the software that they're developing for the electric vehicles that we manufacture and sell in China and Europe. We are using the Enterprise X version. It's self-hosted and on-prem. It's not on the cloud.
Senior DevOps Engineer at a computer software company with 1,001-5,000 employees
Real User
Dec 20, 2022
We use it for development purposes, more specifically for continuous integration to push artifacts for deployment. JFrog is in the middle of both my CI and CD integration.
Our primary use case is for storing the artifacts, dockery majors, or any kind of builds that are created as part of the CI process. Mainly the CI/CD pipelines are what we are using it for.
HPE used JFrog for a lot of things, but my team was building OVAs for VMware. Once the build process was complete, we would upload it to JFrog. There was some other process that would pull it down from JFrog and copy it to AWS for customers to access it. However, I don't think the customers downloaded it from JFrog. They downloaded it from AWS, but it was essentially just a version control for binary bits—artifacts that we created from our build process.
I use it to have a central place to host all my binaries. I also use it to collect any third-party binaries that are needed in my build process so that I always have a copy available in case something happens downstream.
Senior Solutions Architect at a outsourcing company with 51-200 employees
Real User
Jul 11, 2022
Previously, we were developing products without built-in security tools, and Artifactory lets us bake in that security process. We purchased the enterprise edition, which gives us three instances we use in different environments to better deliver our software. We run one instance in a sensitive area that's siloed off, one on our corporate infrastructure, and another on a public Cloud. It could be a customer using something out in the open or on Edge. Artifactory allows us to securely deploy our software.
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...
My main use case for JFrog Artifactory is that we have been using it to manage binaries, which makes it flexible for diverse development. One of the strongest aspects of JFrog Artifactory is its seamless integration with CI/CD pipelines, allowing version control and artifact storage. A specific example of how I use JFrog Artifactory with my CI/CD is that it plays a critical role in improving reproducibility, dependency management, and deployment consistency. My scenario includes storing and building artifacts, managing Docker images, handling dependency caching, and enforcing version control across environments. The main use case and how we are using JFrog Artifactory was multi-package repository support, as we are using it in CI/CD integration and repository replication, access control management, and artifact version tracking, along with Docker registry capabilities.
I have been using JFrog Artifactory for the past three years. We primarily use JFrog Artifactory for storing our Docker images, packages, artifacts, and other files that we use in our applications on a day-to-day basis. In a CI/CD pipeline, there are several workflows and steps where you bundle your code as an image or as an artifact so that you can use it for running the image in containers using Kubernetes. In those stages of the CI/CD pipeline, we generally build the image using Docker. After building the image, we need to store it for future usage. For storing the images that we build using those CI/CD pipelines, we use JFrog Artifactory in our current environment.
JFrog Artifactory is designed for software management. We used it for storing all assets and packages that were downloaded from external package systems, making them available for our development teams to use in their builds. It primarily supported a fail-fast approach, where vulnerabilities were identified ahead of time, enabling us to alert our development team to use the latest packages without those vulnerabilities. JFrog Artifactory proved very helpful in supporting a variety of package types for different projects.
The main use case was to store the artifacts, store the binaries, basically. And then we used it as a container registry as well. One of my tasks was to get X-ray running. I got the product running and tested it, but users never really started using it. So, from the user perspective, I don't really know how much they used X-ray. What I can say about X-ray is that it did what Artifactory advertised. So, from that point of view, in my opinion, it worked fine, but we never really got to use it too deeply. We never got enough requests from our customers, the developers, or the security management team to implement some checks or block downloads from Artifactory, even when the software is too old or has some vulnerabilities. That was a disappointment for me because I worked on the installation and management of X-ray for a couple of months. But that's not something that X-ray is responsible for.
We use Artifactory for all of our software development. We're an electric car company, and we're headquartered in China, but we've got an R&D software development office in San Jose. All of our software development teams use Artifactory for storing all their artifacts, binaries, and things like that for the software that they're developing for the electric vehicles that we manufacture and sell in China and Europe. We are using the Enterprise X version. It's self-hosted and on-prem. It's not on the cloud.
We use it for development purposes, more specifically for continuous integration to push artifacts for deployment. JFrog is in the middle of both my CI and CD integration.
Our primary use case is for storing the artifacts, dockery majors, or any kind of builds that are created as part of the CI process. Mainly the CI/CD pipelines are what we are using it for.
HPE used JFrog for a lot of things, but my team was building OVAs for VMware. Once the build process was complete, we would upload it to JFrog. There was some other process that would pull it down from JFrog and copy it to AWS for customers to access it. However, I don't think the customers downloaded it from JFrog. They downloaded it from AWS, but it was essentially just a version control for binary bits—artifacts that we created from our build process.
I use it to have a central place to host all my binaries. I also use it to collect any third-party binaries that are needed in my build process so that I always have a copy available in case something happens downstream.
Previously, we were developing products without built-in security tools, and Artifactory lets us bake in that security process. We purchased the enterprise edition, which gives us three instances we use in different environments to better deliver our software. We run one instance in a sensitive area that's siloed off, one on our corporate infrastructure, and another on a public Cloud. It could be a customer using something out in the open or on Edge. Artifactory allows us to securely deploy our software.