TrustRadius Insights for Gradle Build Tool (Open Source) are summaries of user sentiment data from TrustRadius reviews and, when necessary, third party data sources.
Pros
Gradle has received positive feedback from reviewers for several key strengths. The intuitive user interface has been consistently praised for its ease of use and efficiency in completing tasks. Many users have stated that the UI allows for quick and efficient task completion. Additionally, several reviewers have mentioned that Gradle's wide language support, particularly for multiple JVM languages like Groovy, has made it accessible to a wide range of computer engineers. This feature enables them to quickly understand and work with Gradle code. Another major strength of Gradle is its support for DSL automation based on Groovy. Users appreciate this feature as it allows for the automation of complex build jobs, making it particularly useful in maintaining and modifying intricate build processes. Overall, these strengths contribute to Gradle's popularity among developers and enhance its usability in diverse development environments.
We use Gradle Build Tool (Open Source) to build all our projects. We switched from Ant/Maven and I love it. No more ugly XML-s and I really like the ability to customize builds with custom tasks. Love the ability to set up remote cache for CI builds.
Pros
Cache
Customizability
Dependency management
Cons
Some options should be set by default like cache-ing.
Authentication to maven repositories should work without any custom tasks
Likelihood to Recommend
Its a solid tool for every job in building Java code. Still has room for improvement but best I ever used!
Gradle Build Tool helped us to build the multiple Android projects in our organization. We have setup the CI/CD pipeline for Automation and build can be created. We have created APK dynamically with the help of Gradle Build Tool and deployed them in both local and production environment. Gradle Build Tool was easily integrate able with the devops tools. Gradle Build Tool helped us to customize our build structure as per the single or multi project builds. We have build projects as well as artifacts used in the projects with its help.
Pros
It support various development environment.
Caching can be enabled which can help in fast build for development environment
It can be easily Integrateable with other devops tools
Cons
Speed for build can be increased
Likelihood to Recommend
Gradle Build Tool is more suitable with the Java projects. It has helped us to automate the build part of the devops cycle. Its configuration and Groovy script is really easy to understand and can be implemented with ease. It can be used both for automation and manual buids of the projects. Gradle Build Tool is easy to use and easy to integrate.
[Gradle is] being used as the build tool of choice for micro services based architecture backend of the next generation cloud product suite. It enables dependency management by referencing to both public and private artifact repositories. Using the cache feature while compiling the codebase it has overall helped to reduce compile time and increase developer productivity
Pros
Build Cache - Enables quick build on dev machines
Supports multi project builds - enabling modular architecture
Customizable build tasks
Support for multiple JVM languages
Cons
Need for ample documentation for its Groovy DSL to write build configs
System File Encoding
Environment variable changes tracking
Likelihood to Recommend
[Gradle is by far the best] and industry leading solution and apt successor for Ant and Maven
Gradle is used as a build tool for the application codebase. Used for both compiling and packaging the artefacts for the projects. Its a good alternative for the Maven build mechanism and dependency management. It aids the CI CD process by seamless dependency management and also developer friendly definition mechanism.
Pros
Compiling and Build process
Artefacts Packaging and publishing
IDE integration for seamless development
Cons
Logging can be improved
dependency management and its eco system
Likelihood to Recommend
Good for using in Microservice based applications. Good for teams which have common developers for both development and DevOps. It can be used for internal artefacts repository also.
VU
Verified User
Program Manager in Information Technology (51-200 employees)
Gradle is being used across the company for the development of Android applications. In the recent times, Gradle has become the standard of development and delivery of Android applications. It helps us in creating different flavors of the build with various parameters. This helps us release multiple versions to different sets of users.
Pros
Integration.
Delivery.
Cons
Technical expertise required.
No easy integration.
Likelihood to Recommend
Gradle is very well suited when you have a basic application that needs to be released to the users. It is also suitable for cases where there may be fragmentation needed to support the release of multiple applications. It is not a tool much needed outside the development of Android applications.
Gradle is the only build tool we use. The Software team uses it to build all of our Java applications. Before, we were using Ant build scripts, but have since completely migrated to Gradle. Gradle, along with Google's Cloud Build, allows us to quickly build our applications in the cloud using automated builds.
Pros
Quick build time for quick deployments!
Integration with IDEs provides ease of use!
Cons
The speed of builds can always be improved.
Needs work for more complex builds like web applications.
Likelihood to Recommend
Gradle is perfectly suited for Java builds. It is very easy to make a template build file and use it across multiple applications. However, we have had some issues implementing Gradle with our web applications.
We are using Gradle as a build tool. We are using it across all the departments in our organization. We are using Gradle to build all our Java applications. We were using Maven before but seeing the advantages of using Gradle we recently migrated all our projects from Maven to Gradle.
Pros
We use it as a build tool.
We build Java applications using this tool.
We also use Gradle to test our apps.
Cons
It becomes a bit tricky when we use Gradle demon.
Likelihood to Recommend
We can use Gradle in many ways, we can build our apps, test apps, and also for dependency management. Gradle manages cache in a very good way. We just need to add a plugin to build and test any Java projects. I don't recommend using Gradle for app deployments, data migrations, etc.
VU
Verified User
Team Lead in Information Technology (1001-5000 employees)
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.
Pros
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
Cons
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
Likelihood to Recommend
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.
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.
Pros
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
Cons
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
Likelihood to Recommend
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.
VU
Verified User
Engineer in Information Technology (11-50 employees)
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.
Pros
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.
Cons
The Gradle documentation is available online, and it is quite comprehensive. However, more real life examples could be useful.
Likelihood to Recommend
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.