JFrog Artifactory vs. RubyGems.org

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

RubyGems is a great packaging library primarily because of its verbose logging information and easy to navigate system architecture. We've dealt with artifactory systems in the past for Java and JavaScript, and RubyGems just makes it a lot easier to handle the packaging and deployment of our reusable libraries. We've noticed in the past that there are times where (if all 200+ teams) are releasing at a similar time that publishing the gems can lag, but that's fairly rare.

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

• Seemless packaging
• Well documented
• Verbose error logs
• Active community support
• Quick security fixes/releases

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

• Lack of solid Windows support.
• Not great performance if lots of people release at the same time.

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.

RubyGems has strong community support and finding issues to errors is as simple as searching for the error message you're receiving (but usually the error is clear enough without having to bother with that). Honestly, the framework is simple enough that support isn't needed much, but it has been helpful to us in the past when we have needed it.

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

RubyGems is easier to use and to troubleshoot issues overall. Sometimes when troubleshooting in other systems errors are masked and it takes a trained eye or a lot of time searching through Google trying to find out what it really means. RubyGems is very verbose and allows for quick troubleshooting of any deployment problems.

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

• Quick package hosting.
• Faster deployment process.
• Less troubleshooting needed during deployment.

Incentivized