JFrog Artifactory is a software repository management solution for enterprises available on-premise or from the cloud, presented as a single solution for housing and managing all the artifacts, binaries, packages, files, containers, and components for use throughout the software supply chain. JFrog Artifactory serves as a central hub for DevOps, integrating with tools and processes to improve automation, increase integrity, and incorporate best practices along the way.
$150
per month
Sauce Labs
Score 7.2 out of 10
N/A
Sauce Labs is a cloud-based platform
for automated testing of desktop and mobile applications. It is designed to be instantly scalable, since it is optimized for continuous
integration workflows. (The vendor says that when tests are automated and run in parallel on
multiple virtual machines across many different browser, platform and device
combinations, testing time is reduced and developer time is freed up from
managing infrastructure.) The Sauce Labs testing cloud is intended to be paired…
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.
Having used some of the competitor's tools over the year I would say that SauceLabs provides a lot of value for money if you plan to run long sets of tests with high frequencies. Paying for a single slot means you can run tests whenever you want without creeping costs but it does make running tests in parallel require an extra slot. Currently, our test suite takes over three hours to run and at the moment it is cost prohibitive to purchase an extra slot. However, having access to live testing and integration with Appium is great.
I've had four changes in account managers over the past couple of years. They ranged from super experienced/advocate to some that seems relatively junior/a bit removed. I understand this happens but clarity on what I can expect with these partnerships would be valuable. What I've gotten in the end has varied dramatically.
As we currently know, there's nothing on the market with a big feature set like saucelabs at their current price point. Along with the business not having to learn a whole new tool to use again and the ability to refresh our private devices and the continuously growing number of public devices available and features.
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.
It is an incredibly easy service to use for what its primary intention is. The only reason a point is deducted is because more feature enrichment can be done around the Sauce Connect Proxy utility and the Jenkins Sauce OnDemand plugin. User Account administration also needs more work, such as the addition of user groups, rather than a simple hierarchy of users.
Yes, Sauce labs is always there, and it is easy to troubleshoot when you are having any connectivity issue, they always keep you informed when they plan to perform any type of maintenance window on their side in advance, so you can plan and will not affect your current work. I do not recall any outage.
The time where they acquired TestObject and were trying to integrate their services would probably be the most annoying time. Annoying as features were in two separate places (websites) for example. But since the introduction of their unified platform, we haven't run into any issues as of yet and we've used them for at least 5-6 years now.
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.
The people here are just so friendly and personable. For instance, Tristan Lombard answered every single email with a very cheery tone and not only did he diagnose my issue, he also made sure to ask how my day was going. Keep it up
I am not sure if it's my company that makes getting Sauce Labs integrated into the team difficult or is it Sauce Labs. The process for getting Sauce Labs for a project is quite a tedious process and the information for using Sauce Labs initially is quite lacking. There is little support for getting started
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.
We have also tested out Browser Stack, which at the time was more geared towards manual testing. Although it appeared to support more mobile devices/browsers, we also wanted something that can plugin in easily with our existing Selenium test scripts. Sauce Labs was definitely more geared towards our goals at the moment which were to automation functional/regression testing and build it into our release pipeline.
With private devices, you have full reign over usage of them, so no complaints there. Public devices are available if no one else is using it, which is understandable. Browser VMs are based on number of open sessions and Saucelabs give you a certain number depending on what you need. If you need more, then you pay for more. It is as simple as that. You need more devices, then you can pay for more private ones too. A workaround for public devices is to pick the first available one and not be too picky, that's if you are able to of course.
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.
