Azure Artifacts vs. JFrog Artifactory vs. Pulp

Share codes and packages across the whole organization. We have developers most of the time work from home or overseas like in India. We can test and deploy the package when they deploy the new changes into the Azure Artifacts. Azure Artifact can promote our package to the correct system like DEV, UAT, or Production. It also provides retention policies to automatically clean up expired packages.

Incentivized

It works at scale and a large number of accessible pipelines for searching, repository updates and indexing will become easier. JFrog provides end-to-end solutions for all DevOps needs. With this, Jfrog Artifactory specifically implements the management of highly available repositories, with a smooth interface and integration with all the main CI tools on the market.

Incentivized

I understand that this tool may not be for everyone, but it served its purpose perfectly for us. It allows us to safely change to older repositories in case we need to roll back any changes. It has definitely reduced operational costs for us due to allowing us to safely manage our own packages without relying solely on external providers, which are not always reliable. However, it's worth mentioning that the setup/maintenance can be a little bit fiddly for some users. There's a learning curve here, but, to us, it was totally worth it.

• Security feature on share code efficiently.
• The built in CI/CD for the software pipeline.
• Support for most famous build tool like maven and npm.

Incentivized

• Artifactory Management acting as a repository manager of docker images, application and component dependencies
• Automate pipelines and thereby releasing changes faster
• Supports high availability and scalability with multi site replication

Incentivized

• Native artifact format support like docker image
• Support for APL
• Support IAM permission

Incentivized

• We can always use support for more different types of packages in Artifactory.
• We also would like to see the Artifactory X-Ray produce continue to mature.

Incentivized

The main problem that seems intractable is getting the checksum of the artifact. Managing container artifacts is a game changer for us during project execution, as the container artifact type exposes all base image and Docker file steps. This makes debugging or analysis easier. Jfrog Artifactory provides promotion feature and can automated from one environment repo to another environment repo before the deployment occurs.

Incentivized

Support tickets take days to respond. The most basic of questions that should be knocked out in a few hours don't get answers for days. Tickets are also closed without resolution.

Azure Artifact is based on GitHub which is the best artifact at all times. Helm is open source and we may have security concerns. Crucible is a good tool but does not of a lot of support. I prefer that Azure Artifact is a solid product and with a good gene from the GitHub codebase.

Incentivized

JFrog Artifactory has a much more friendly GUI, making package exploration less of a chore to do. Other than that, their features are pretty much comparable to each other. Both support multiple types of packages; both have API that can integrate well with CI/CD pipelines.

Incentivized

• The artifact provide best practice to our software development.
• Provide a standard way to release the software.
• The package is immutability which means no one can update it after release.

Incentivized

• 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.

Incentivized