TrustRadius
Gradle is an open source build system.https://media.trustradius.com/product-logos/Ua/Fg/L6Q5QR1XSLQP.pngGradle when you want toGradle is being used to build the server service. We use it to compile Java, run tests, and some of the deployment work. The backend team uses the service, as well as the integration test project. Gradle allows us to share the build process between developers and the various build machines.,It allows us to share configurations between machines and developers It makes builds reproducible It allows us to tweak how our server gets bundled and deployed,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,4,Gradle has been a roadblock lately to our move to another hosting service Developers can't get started on a project with the latest tools, leading to delays in change efforts Gradle builds can be fast, once up and running, allowing for faster development turnaround,Apache Maven,Eclipse, Sublime Text, Docker,3I like Gradle!!!We currently use Gradle to manage the build lifecycle of our applications. It's used by the IT department, we are currently using it with applications written in Java and Groovy as well.,It's highly customizable and easy to understand It's quite simple to write an additional plugin if that's necessary Provides support for Groovy and the latest versions also support Kotlin The gradle wrapper is awesome because it allows to use Gradle without installing it,I'd like to see a way to specify how to run only certain tests in parallel, I tried this feature and for tests that involve interaction with SQL Databases sometimes I can't because of deadlocks. Not sure if there is something else, gradle has been working really good for us and they are adding improvements all the time which is awesome. I used to think the performance is a deal but the latest versions are addressing this issue very well,10,Accelerate the build process of our applications We can trigger tests in parallel which is worth for CI servers Easy to understand and extend if that's needed,Apache Maven, SBT and Grunt,Oracle Java SE, Springs.io, Apache Maven, MySQL, Cassandra, JRebel, AWS LambdaThe future of CI/CD with Gradle - moving forward.In my organization, Gradle is being used in conjunction with Jenkins, to support a model of Continuous Integration. It is being used across a distributed organization, encompassing three geographic locations. It addresses the business model of CI/CD. With Gradle we were able to automate the building of a complex backend application, supporting a variety of branches, daily builds, and distributed development teams.,Gradle's methods to manipulate files is very flexible. It minimizes the amount of code one has to write to copy, move, or expand zip or tar files. Gradle uses Groovy, which is a Java like language. This allows for most computer engineers to come up to speed fairly quickly, for writing or maintaining gradle code. Gradle also supports DSL (Domain Specific Language), which is based on Groovy. The DSL language allows engineers to automate build jobs that otherwise could be very cumbersome to maintain or modify.,The Gradle documentation is available online, and it is quite comprehensive. However, more real life examples could be useful.,10,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.,,JenkinsGradle - a modern MavenI use Gradle when developing Java applications in both professional and personal/academic projects. It is a great tool when building said applications with plug-ins and frameworks available in the community.,Cross-version compatibility testing Inspection of build outcome and output Build automatically when sources change Continuous build detects changes that occur during build execution,Ease of use Gradle's configuration isn't always intuitive Changing a project from Maven to gradle sometimes proves to be a difficult task,8,Less time fixing framework compatibility problems Less time when changing frameworks or plug-ins,MavenGradle is easy to read, very portable, and customizable with Groovy dslWe use it for all of our build management software, from testing, building, to deploys.,Portability Ease of customization Ease of readability,Better integration with IntelliJ. I have to hit refresh on Intellij Gradle tool window all the time. Better speed.,10,Dependable builds. Reliable builds.,apache ant and Apache Maven,Java Reporting Engine
  3. Gradle Reviews
Unspecified
Gradle
22 Ratings
Score 7.2 out of 101
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener noreferrer'>trScore algorithm: Learn more.</a>TRScore

Gradle Reviews

Gradle
22 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener noreferrer'>trScore algorithm: Learn more.</a>
Score 7.2 out of 101

Do you work for this company?

Show Filters 
Hide Filters 
Filter 22 vetted Gradle reviews and ratings
Clear all filters
Overall Rating
Reviewer's Company Size
Last Updated
By Topic
Industry
Department
Experience
Job Type
Role
Show All Filters
More Filters 
Less Filters 

Reviews (1-5 of 5)

Companies can't remove reviews or game the system. Here's why.
David Tanner profile photo
May 14, 2019

Gradle when you want to

David Tanner
Score 4 out of 10
Vetted Review
Verified User
Review Source
Gradle is being used to build the server service. We use it to compile Java, run tests, and some of the deployment work. The backend team uses the service, as well as the integration test project. Gradle allows us to share the build process between developers and the various build machines.
  • It allows us to share configurations between machines and developers
  • It makes builds reproducible
  • It allows us to tweak how our server gets bundled and deployed
  • 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
Gradle seems to be the new kid on the block, and provides better support for parallel tasks. Getting started can be very easy, but projects quickly need more control, or customization which Gradle has a hard time providing. The rapid changes to the tool also make it difficult for organizations that aren't actively developing in Gradle, and so the tool might be better suited to companies willing to spend the time on the build configuration.
Read David Tanner's full review
No photo available
January 24, 2018

I like Gradle!!!

Verified User
Score 10 out of 10
Vetted Review
Verified User
Review Source
We currently use Gradle to manage the build lifecycle of our applications. It's used by the IT department, we are currently using it with applications written in Java and Groovy as well.

  • It's highly customizable and easy to understand
  • It's quite simple to write an additional plugin if that's necessary
  • Provides support for Groovy and the latest versions also support Kotlin
  • The gradle wrapper is awesome because it allows to use Gradle without installing it
  • I'd like to see a way to specify how to run only certain tests in parallel, I tried this feature and for tests that involve interaction with SQL Databases sometimes I can't because of deadlocks.
  • Not sure if there is something else, gradle has been working really good for us and they are adding improvements all the time which is awesome. I used to think the performance is a deal but the latest versions are addressing this issue very well
I highly recommend Gradle to manage the build lifecycle of applications, we have been using it with Java and Groovy applications, mainly with spring-boot to build microservices oriented systems.

I don't recommend using it for Scala applications since SBT would be a better choice for it.
Read this authenticated review
Dirce Richards profile photo
April 13, 2017

The future of CI/CD with Gradle - moving forward.

Dirce Richards
Score 10 out of 10
Vetted Review
Verified User
Review Source
In my organization, Gradle is being used in conjunction with Jenkins, to support a model of Continuous Integration. It is being used across a distributed organization, encompassing three geographic locations. It addresses the business model of CI/CD. With Gradle we were able to automate the building of a complex backend application, supporting a variety of branches, daily builds, and distributed development teams.
  • Gradle's methods to manipulate files is very flexible. It minimizes the amount of code one has to write to copy, move, or expand zip or tar files.
  • Gradle uses Groovy, which is a Java like language. This allows for most computer engineers to come up to speed fairly quickly, for writing or maintaining gradle code.
  • Gradle also supports DSL (Domain Specific Language), which is based on Groovy. The DSL language allows engineers to automate build jobs that otherwise could be very cumbersome to maintain or modify.
  • The Gradle documentation is available online, and it is quite comprehensive. However, more real life examples could be useful.
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 Dirce Richards's full review
Gabriel Freire profile photo
January 23, 2017

Gradle - a modern Maven

Gabriel Freire
Score 8 out of 10
Vetted Review
Verified User
Review Source
I use Gradle when developing Java applications in both professional and personal/academic projects. It is a great tool when building said applications with plug-ins and frameworks available in the community.
  • Cross-version compatibility testing
  • Inspection of build outcome and output
  • Build automatically when sources change
  • Continuous build detects changes that occur during build execution
  • Ease of use
  • Gradle's configuration isn't always intuitive
  • Changing a project from Maven to gradle sometimes proves to be a difficult task
I'd say Gradle is very well suited for Java projects that require managing lots of plug-ins and frameworks but I don't think it's well suited for project builds with other programming languages.
Read Gabriel Freire's full review
No photo available
March 29, 2017

Gradle is easy to read, very portable, and customizable with Groovy dsl

Verified User
Score 10 out of 10
Vetted Review
Verified User
Review Source
We use it for all of our build management software, from testing, building, to deploys.
  • Portability
  • Ease of customization
  • Ease of readability
  • Better integration with IntelliJ. I have to hit refresh on Intellij Gradle tool window all the time.
  • Better speed.
[Gradle is well suited for] All Java, Kotlin, Scala language projects. Probably not suited for legacy maven projects.
Read this authenticated review

Gradle Scorecard Summary

Likelihood to Recommend (22)
7.2
Performance (1)
3.0

About Gradle

Gradle is an open source build system.
Categories:  Build Automation

Gradle Technical Details

Operating Systems: Unspecified
Mobile Application:No