JFrog Artifactory vs. Visual Studio App Center

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

Honestly, it's an all around solution that needs some enhancements. Need to build an app, check! Need to test that app, check! Need to debug that app, check! Visual Studio App Center is a well rounded platform for multiple types of builds and services.

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

• It supplies the right native integration for test cases both IOS and Android
• Constant device updates means you are working with the right builds to support product use cases
• Excels in automated test cases that are easy to implement, monitor, and digest results

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

• Webview support was lacking
• User management seems a bit disconnected from the standard Microsoft ecosystem. Almost feels like you are managing local users and sharing access more than an enterprise solution
• Price could be better
• Buggy on some of the latest versions of windows

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 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 biggest benefit is in integrations and plug-ins, as well as the fact that it's not open source. I know open source is popular, but we have all been on the downside of open source and waiting for things to be voted up or a contribution to fix an issue. This alone makes VSAC a nice solution! Plus, it comes with a complete IDE integration of services, documentation, and is light weight

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

• Cut down on time to delivery enhancements and overall builds to users
• Helps test new proposed releases with ease
• Cuts down on local build issues as it does do a good job with local development environments as well

Incentivized