Browse Library
Sign In Start Free Trial
Close icon Search icon
Account
Browse Library Advanced Search Sign In Start Free Trial

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Mastering Gradle
  • Toc
  • feedback
Mastering Gradle

Mastering Gradle

By : Mitra
3 (4)
close
Mastering Gradle

Mastering Gradle

3 (4)
By: Mitra

Overview of this book

If you are a developer with some experience in build tool and want to become an expert in build tool, then this book is for you. Basic knowledge of Gradle or any other build tool is essential.
Table of Contents (12 chapters)
close
close
Preface
Preface
What this book covers
What you need for this book
Who this book is for
Conventions
Reader feedback
Customer support
Free Chapter
1
1. Getting Started with Gradle
chevron up
1. Getting Started with Gradle
Understanding Build Automation System
Gradle overview
Installation and quick start
Our first script
Gradle command Line arguments
The Gradle GUI
Start up script
Build life cycle
Cache management
Gradle with IDE
Summary
2
2. Groovy Essentials for Gradle
2. Groovy Essentials for Gradle
Overview
Groovy script for Hello World
Data types
Classes, beans, and methods
Control structures
Collections
Closure
Builder
Summary
3
3. Managing Task
3. Managing Task
Build script basics
Task configuration
Task execution
Task dependency
Task ordering
Task operations
Gradle's in-built tasks
Custom tasks
Summary
4
4. Plugin Management
4. Plugin Management
The script plugin
The binary plugin
Gradle's in-built plugins
The Java plugin
The custom plugin
Summary
5
5. Dependency Management
5. Dependency Management
Overview
Dependency configurations
Dependency resolution
Customizing the dependency
Publishing artifacts
Summary
6
6. Working with Gradle
6. Working with Gradle
The War plugin
The Scala plugin
Logging
File management
Property management
Multi-project build
Testing with Gradle
Summary
7
7. Continuous Integration
7. Continuous Integration
Jenkins walk-through
Checkstyle and PMD plugins
The Sonar Runner plugin
TeamCity walk-through
Summary
8
8. Migration
8. Migration
Migration from Ant
Migration from Maven
Summary
9
9. Deployment
9. Deployment
Role of Gradle in deployment
Docker overview
Installing Docker
Docker commands
Running an application in Docker
Build, Deployment, and Test pipeline
Summary
10
10. Building Android Applications with Gradle
10. Building Android Applications with Gradle
Creating Android project using Android Studio
Building the Android project with Gradle
Summary
11
Index
Index

Build life cycle

Gradle build has a life cycle, which consists of three phases: initialization, configuration, and execution. Understanding the build life cycle and the execution phases is crucial for Gradle developers. Gradle build is primarily a collection of tasks and a user can define the dependency between the tasks. So, even if two tasks depend on the same task, for example, Task C and Task B both depend on Task A, Gradle makes sure that Task A will execute only once throughout the execution of the build script.

Before executing any task, Gradle prepares a Directed Acyclic Graph (DAG) of all tasks for the build. It is directed because a task directly depends on another task. It is acyclic because, if Task A depends on Task B and if you make Task B depend on Task A, it will result in an error, as there can't be cyclic dependency between two tasks. Before executing the build script, Gradle configures the task dependency graph.

Let's quickly discuss the three build phases.

Initialization

User can create a build script for a single project as well as for a Multi-project build. During the initialization phase, Gradle determines which projects are going to take part in the build process, and creates a Project instance for each of these projects.

Configuration

This phase configures the project object. All the build scripts (in case the user is executing a multiproject build), which are part of the build process are executed without executing any task. This means whatever statements you have written outside of the task in the configuration block would be executed in the configuration phase. No tasks would be executed here; only the directed acyclic graph would be created for all tasks.

Execution

In this phase, Gradle executes all tasks as per the order given in the command line. However, if any dependencies exist between tasks, those relationships will be honored first before the command-line ordering.

End of Section 9
Next Section
bookmark search playlist font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected
Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete