JFrog Artifactory vs. NuGet

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

If you're working on some .NET Framework / .NET Core projects, there's no other real choice here. NuGet works well, the heavy reliance on built-in GUI makes it friendly & easy-to-learn for new people, especially those who haven't been used to dependency management topics. But for those coming from the Java world, who are already spoiled by text-based Maven / Ivy, then NuGet could be a chore to work on a daily basis.

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

• The built-in package explorer / manager in Visual Studio work reliably
• Integration with popular web-based repository manager is good
• Command-line options are enough even for complex use cases like publishing to private, credentials-protected repositories

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

• Incomplete download resume in case of network disruptions
• Adding user friendly platform to add and update the packages
• Package creation option in Visual Studio

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.

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

Didn't use another package manager as NuGet was our favorite since the beginning.

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

• Saves a rework by sharing the common functionalities across the projects
• Helped to optimize the given package using a central repository
• Helped to make use of existing useful packages

Incentivized