Azure DevOps Services vs. Gradle Build Tool (Open Source)

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
Azure DevOps Services
Score 8.6 out of 10
N/A
Azure DevOps (formerly VSTS, Microsoft Visual Studio Team System) is an agile development product that is an extension of the Microsoft Visual Studio architecture. Azure DevOps includes software development, collaboration, and reporting capabilities.
$2
per GB (first 2GB free)
Gradle Build Tool (Open Source)
Score 8.5 out of 10
N/A
Gradle is an open source build system. Gradle boasts a rich API and mature ecosystem of plugins and integrations to support automation. Users can model, integrate and systematize the delivery of software from end to end.
$0
per month
Pricing
Azure DevOps ServicesGradle Build Tool (Open Source)
Editions & Modules
Azure Artifacts
$2
per GB (first 2GB free)
Basic Plan
$6
per user per month (first 5 users free)
Azure Pipelines - Self-Hosted
$15
per extra parallel job (1 free parallel job with unlimited minutes)
Azure Pipelines - Microsoft Hosted
$40
per parallel job (1,800 minutes free with 1 free parallel job)
Basic + Test Plan
$52
per user per month
No answers on this topic
Offerings
Pricing Offerings
Azure DevOps ServicesGradle Build Tool (Open Source)
Free Trial
NoNo
Free/Freemium Version
NoYes
Premium Consulting/Integration Services
NoNo
More Pricing Information
Community Pulse
Azure DevOps ServicesGradle Build Tool (Open Source)
Considered Both Products
Azure DevOps Services
Chose Azure DevOps Services
With more functionality added, JIRA has become slow, whereas VSTS is a pleasure to use. Trac and JIRA do not show the entire health status of the pipeline like VSTS. Hygieia is open source and trying to achieve what VSTS does but it is not as mature yet.
Gradle Build Tool (Open Source)

No answer on this topic

Top Pros

No answers on this topic

Top Cons

No answers on this topic

User Ratings
Azure DevOps ServicesGradle Build Tool (Open Source)
Likelihood to Recommend
8.8
(54 ratings)
9.4
(10 ratings)
Likelihood to Renew
10.0
(3 ratings)
-
(0 ratings)
Usability
7.0
(5 ratings)
10.0
(1 ratings)
Performance
-
(0 ratings)
3.0
(2 ratings)
Support Rating
8.1
(20 ratings)
9.0
(7 ratings)
Implementation Rating
10.0
(2 ratings)
-
(0 ratings)
User Testimonials
Azure DevOps ServicesGradle Build Tool (Open Source)
Likelihood to Recommend
Microsoft
Before using Azure DevOps, the department was calculating metrics by hand. It was a very tedious process that, at times required duplicate effort. Once we added the online boards, we were able to let the cards automatically calculate dates and provide us with team metrics instantly. It is also great for being able to easily move features from one team to another. Before we added all teams in the same project, it would require us to re-enter the features. We move features around a lot so that has been a big help. I also like the board customization, not all of our teams follow the exact same Agile flow, so allowing each board to have its own columns, states, and notifications give flexibility to each team.
Read full review
Open Source
Gradle is an ideal tool to build an application that is complex and/or distributed. It is well suited for builds that use a CI engine such as Jenkins or Bamboo, and a repository such as Artifactory.
Read full review
Pros
Microsoft
  • Flexible Requirements Hierarchy Management: AZDO makes it easy to track items such as features or epics as a flat list, or as a hierarchy in which you can track the parent-child relationship.
  • Fast Data Entry: AZDO was designed to facilitate quick data entry to capture work items quickly, while still enabling detailed capture of acceptance criteria and item properties.
  • Excel Integration: AZDO stands out for its integration with MS Excel, which enables quick updates for bulk items.
Read full review
Open Source
  • Build Cache - Enables quick build on dev machines
  • Supports multi project builds - enabling modular architecture
  • Customizable build tasks
  • Support for multiple JVM languages
Read full review
Cons
Microsoft
  • Need to make the changes so that it doesn't occupy most of the CPU utilization and memory
  • Execution of Bulky SQl Queries leads to either the SQl being out of exception or the VS being unresponsive
  • Integration with Microsoft products is easy, but with non-Microsoft products it is more difficult, and you have to make a lot of configuration changes to integrate
  • With every upgrade of the Visual Studio, like from VS 2010 to VS 2013 , we need to upgrade our hardware/machine, as the VS hardware requirement also increases
  • If code is getting compiled in one visual studio, like in VS 2010, that the same code could possibly give an error when compiled in VS 2013, due to certain changes in keyword, data format, etc., with the VS upgrade
Read full review
Open Source
  • Still under development, not as mature as Maven
  • Build files aren't as easy to follow because they are so loose
  • The community isn't as large as Maven
Read full review
Likelihood to Renew
Microsoft
I don't think our organization will stray from using VSTS/TFS as we are now looking to upgrade to the 2012 version. Since our business is software development and we want to meet the requirements of CMMI to deliver consistent and high quality software, this SDLC management tool is here to stay. In addition, our company uses a lot of Microsoft products, such as Office 365, Asp.net, etc, and since VSTS/TFS has proved itself invaluable to our own processes and is within the Microsoft family of products, we will continue to use VSTS/TFS for a long, long time.
Read full review
Open Source
No answers on this topic
Usability
Microsoft
Azure DevOps is a powerful, complex cloud application. As such there are a number of things it does great and something where there is room for improvement. One of those areas would be in usability. In my opinion it relies too much on search. There is no easy way to view all projects or to group them in a logical way. You need to search for everything.
Read full review
Open Source
Gradle's language construct is good
Read full review
Performance
Microsoft
No answers on this topic
Open Source
I have tried to use Gradle for projects several times in the past, but there is just so much work in maintaining the build file that it quickly becomes untenable. I have been using Maven for many years, and even though the build file can be complex, it works without maintenance between releases.
Read full review
Support Rating
Microsoft
When we've had issues, both Microsoft support and the user community have been very responsive. DevOps has an active developer community and frankly, you can find most of your questions already asked and answered there. Microsoft also does a better job than most software vendors I've worked with creating detailed and frequently updated documentation.
Read full review
Open Source
Gradle has been an excellent tool for Android development. It has helped us create multiple versions of the app for different environments. It also takes care of all the packaging needs in the background without having to write all the code related to that. It is a no brainer to use Gradle with Android applications.
Read full review
Implementation Rating
Microsoft
Was not part of the process.
Read full review
Open Source
No answers on this topic
Alternatives Considered
Microsoft
VSTS is great if you final source system is Microsoft based. Everything work well together and once you learned how use VSTS it isn't difficult to build more build systems. If your staff are used to the methods Microsoft uses, their time learning VSTS won't be as difficult as staff that do not know the Microsoft way of doing things. If, however, you are going to build non-Microsoft bases applications, such as Java, Ruby or even Python, Jenkins is probably a better choice.
Read full review
Open Source
SBT works fine for Scala but when I tried to use it with Java it was hard to configure and I gave up. Maven is awesome but the pom.xml file tends to be really big which makes it hard to read. Grunt is suitable only for js projects.
Read full review
Return on Investment
Microsoft
  • Via acquisition, we had some Atlassian tools including Jira, bitbucket, and confluence licenses. Total cost for 25 users was close to $5000. Migrating the team to VSTS would net savings of close to $2500.
  • If you're running TFS, you can save costs on: server licenses (you'll have at least 2 - one TFS, one build server). Save time on maintenance and upgrades of TFS.
Read full review
Open Source
  • In a distributed development environment, once we established a strong CI/CD model, Gradle proved to be a great choice to automate the various processes. Gradle also provides much flexibility, which is essential in today's development environment. The important benefit is that the CI/CD engineers can support development's needs quickly and reliably. This in turn supports faster testing and deployment, which generates higher ROI.
Read full review