Azure Artifacts vs. JFrog Artifactory

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

• 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

• Stores and Manages build artifacts and packages.
• Works as container registry as well.
• Easily manages local and remote repositories along with live replication.

Incentivized

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

Incentivized

• CI/CD integration. We understood they do have a pipeline, so our organization already started with Jenkins, and my understanding is that not many orgs are using the JFrog pipeline.

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 pipelines are being used in the same ecosystem as an integrated environment, to support CI-CD devops journey. This eventually helps the existing team to use both the features of the same product in a seamless way.Similar Xray, can be used as a secure measure to protect your containers and can be used as a Static Code analysis tool which can also be integrated in a Devops CI pipeline as a Left shift security strategy.

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

• We now have a solid, reliable binary repository that can survive a regional outage in AWS when deployed properly
• It has allowed us to focus on building mature CICD pipelines without having to worry about an unreliable binary repository.

Incentivized