GoCD vs. Gradle Build Tool (Open Source)

GoCD is easy to set up. So if you just want to get some pipelines up & running quickly, & they're quite stable, or you can have many pipelines for different needs then GoCD is great. Still, if you only want to have a few pipelines, but with the flexibility to run them with different parameters dynamically, then Jenkins is better.

Incentivized

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.

• Pipeline-as-Code works really well. All our pipelines are defined in yml files, which are checked into SCM.
• The ability to link multiple pipelines together is really cool. Later pipelines can declare a dependency to pick up the build artifacts of earlier ones.
• Agents definition is really great. We can define multiple different kinds of environments to best suit our diverse build systems.

Incentivized

• 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

Incentivized

• UI can be improved
• Location for settings can be re-arranged
• API for setting up pipeline

Incentivized

• 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

Incentivized

Gradle's language construct is good

Incentivized

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.

Incentivized

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.

Incentivized

I prefer using GoCD compared to Jenkins. The UI makes sense, I like the simplicity to hit the 'Play' button for a straightforward deployment of the 'Play +' if you need to override some settings when deploying whereas Jenkins, you have the whole page for each pipeline. The environment makes sense but can often confuse the user while GoCD simply has a drop-down to select your environment.

Incentivized

[Gradle is] a more modern version of open source build tools like Ant and Maven.
Whereas the build config was XML files which were tedious and error
prone, the modern DSL usage of Groovy to write these build files is a
great advancement. Also these config files can be inherited from top
level to each associated project.

Incentivized

• ROI has been good since it's open source
• Settings.xml need to be backed up periodically. It contains all the settings for your pipelines! We accidentally deleted before and we have to restore and re-create several missing pipelines
• More straight forward use of API and allows filtering e.g., pull all pipelines triggered after this date

Incentivized

• 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.

Incentivized