Filter Ratings and Reviews
Filter 26 vetted Gradle reviews and ratings
Reviews (1-8 of 8)
December 16, 2019
Great tool to use, especially for Android developers
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.
- Integration.
- Delivery.
- Technical expertise required.
- No easy integration.
November 11, 2019
Gradle Serves As A Perfect Build Tool For Java 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.
- Quick build time for quick deployments!
- Integration with IDEs provides ease of use!
- The speed of builds can always be improved.
- Needs work for more complex builds like 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.
- We use it as a build tool.
- We build Java applications using this tool.
- We also use Gradle to test our apps.
- It becomes a bit tricky when we use Gradle demon.
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
April 13, 2017
The 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.
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
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
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 Scorecard Summary
About Gradle
Gradle is an open source build system.
Categories: Build Automation
Gradle Technical Details
| Operating Systems: | Unspecified |
|---|---|
| Mobile Application: | No |