Book Image

Gradle Essentials

By : Kunal Dabir, Abhinandan Maheshwari
Book Image

Gradle Essentials

By: Kunal Dabir, Abhinandan Maheshwari

Overview of this book

Gradle is an advanced and modern build automation tool. It inherits the best elements of the past generation of build tools, but it also differs and innovates to bring terseness, elegance, simplicity, and the flexibility to build. Right from installing Gradle and writing your first build file to creating a fully-fledged multi-module project build, this book will guide you through its topics in a step-by-step fashion. You will get your hands dirty with a simple Java project built with Gradle and go on to build web applications that are run with Jetty or Tomcat. We take a unique approach towards explaining the DSL using the Gradle API, which makes the DSL more accessible and intuitive. All in all, this book is a concise guide to help you decipher the Gradle build files, covering the essential topics that are most useful in real-world projects. With every chapter, you will learn a new topic and be able to readily implement your build files.
Table of Contents (17 chapters)
Gradle Essentials
About the Authors
About the Reviewers

Continuous Integration

Continuous Integration (CI) is one of the most popular buzzwords you can read everywhere. As is apparent from its name, CI is the process of integrating the code base each time; whenever any one makes commits to the repository. It compiles the code, run the unit test cases and prepare the build. One of the benefits a user gets here is, if there are compile issues and integration issues, a user can figure out at early stages, rather than it being too late. The following is the generic workflow the CI tool follows:

Figure 6.1

How does Gradle fit into this flow? To plan the build and deployment automation solution for any software, we need a different set of tools to work together to achieve the common goal. Jenkins is one of the integration tools that helps to integrate the complete workflow. It also works on the concept of plugins; you can add different plugins to Jenkins (for example, Gradle, Git, Svn, and so on) as per your need and configure them to plan the automation...