Gradle Build Tool (Open Source) vs. Jenkins

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
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
Jenkins
Score 8.4 out of 10
N/A
Jenkins is an open source automation server. Jenkins provides hundreds of plugins to support building, deploying and automating any project. As an extensible automation server, Jenkins can be used as a simple CI server or turned into a continuous delivery hub for any project.N/A
Pricing
Gradle Build Tool (Open Source)Jenkins
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Gradle Build Tool (Open Source)Jenkins
Free Trial
NoNo
Free/Freemium Version
YesYes
Premium Consulting/Integration Services
NoNo
More Pricing Information
Community Pulse
Gradle Build Tool (Open Source)Jenkins
Considered Both Products
Gradle Build Tool (Open Source)
Chose Gradle Build Tool (Open Source)
I have participated in a variety of build environments, from basic shell scripts, to ant, and to maven. All of these tools have a place, sometimes perhaps in legacy code. But moving forward, I would never go back to other more primitive tools (never say never...). The more I …
Jenkins

No answer on this topic

Top Pros

No answers on this topic

Top Cons

No answers on this topic

User Ratings
Gradle Build Tool (Open Source)Jenkins
Likelihood to Recommend
9.4
(10 ratings)
8.3
(55 ratings)
Usability
10.0
(1 ratings)
5.0
(3 ratings)
Performance
3.0
(2 ratings)
8.9
(12 ratings)
Support Rating
9.0
(7 ratings)
6.6
(12 ratings)
User Testimonials
Gradle Build Tool (Open Source)Jenkins
Likelihood to Recommend
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
Open Source
Jenkins helps the flow of build from the development team to the QA team. Can be really helpful in doing continuous builds, but when this feature is turned on the development team must have great communication otherwise the risk of broken builds become very high. In the long run, we found it made things easier when we just pushed the build manually and appointed a team member the build master.
Read full review
Pros
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
Open Source
  • Automatic jobs: there are infinite possibilities when it comes to Jenkins. You can run code against any testing suite you can imagine or conjure up. You can deploy applications at any time anywhere, automatically with no human intervention. If a certain stage fails, it will notify the team and your sysadmin of the issue so you can resolve it as quickly as possible
  • Automatic rollback: because of how Jenkins works, it can hold off publishing code and integrate locally to run QA procedures before pushing to deployment. This means that bugs are caught before your servers are updated and prevents a faulty program from affecting your downtime in the first place. Its a game changer for high availability.
Read full review
Cons
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
Open Source
  • Once we organized a hackathon with our GitHub Storage. Jenkins was integrated at that time. We had a 20GB plan, but it oversized to 50GB. We had to bear a large sum of money which was unpredicted by our company. Being a startup we cannot bear such mistakes.
  • Jenkins cannot be easily studied and managed. We have to recruit personnel part-time for managing and servicing the server.
  • Though it is open source, there is no dedicated community driven forum or support. There are 3rd party discussion and support portals. Thus, we use Gitter always for debugging and solutions.
Read full review
Usability
Open Source
Gradle's language construct is good
Read full review
Open Source
While the day to day use is very easy, the configuration and setting up of the system or new projects can be cumbersome.
Read full review
Performance
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
Open Source
Sometimes I feel like I am using software developed at the '90s. The Jenkins functioning is amazing. It fulfills its role, but when we are talking about the user interface, it is something painful sometimes, and unfortunately, I didn't see investment and/or improvement on this part over the past few years. Another thing I couldn't forget to mention is about the ecosystem around Jenkins, there are a bunch of plugins, but due to this flexibility, we caught ourselves struggling with broken plugins several times.
Read full review
Support Rating
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
Open Source
There is a large development community - but it is shifting as people move towards other tools. A lot of companies still use Jenkins and will build propriety tools, which doesn't help any of the open-source community. Jenkins has a lot of help and support online, but other, more modern, alternatives will have better support for newer tech.
Read full review
Alternatives Considered
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
Open Source
We previously utilized Hudson - which was limited and did not have the extensive plugin abilities of Jenkins. We selected Jenkins for it's ease of use, beautiful interface, and stability. Other software such as Hudson and Bamboo didn't provide these abilities.
Read full review
Return on Investment
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
Open Source
  • Low investment: As the software is open source, there is no purchase required for on-premises installations, and there is a low barrier to entry for companies offering hosted solutions. This leads to competition on price, and therefore lower prices.
  • Saves time by automating manual tasks: There are often a lot of repetitive tasks that need to be done to prepare for a release, and Jenkins enables these tasks to be run easily and frequently (for example, running tasks on every pull request)
  • Near-immediate returns: Spend a day or two and easily automate most common tasks. Reports are visible so that managers and team leads can keep an eye on code quality.
Read full review