Groovy & Gradle: JVM Automation and Build Engineering · 课时

任务与构建生命周期

定义和管理 Gradle 任务，了解任务依赖关系，并掌握构建生命周期的各个阶段。

任务与构建生命周期 是 CoddyKit 上的免费 Groovy & Gradle: JVM Automation and Build Engineering 课时。这是第 3 节课，共 4 节。你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。这是 Groovy & Gradle: JVM Automation and Build Engineering 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 Groovy & Gradle: JVM Automation and Build Engineering 课程共包含 4 节课。

本课时的部分内容尚未翻译，以英文显示。

What are Gradle Tasks?

Welcome! In this lesson, we'll dive into Gradle Tasks, the fundamental units of work in any Gradle build.

A task represents a single, atomic piece of work that Gradle performs.
Think of tasks as actions like 'compile code', 'run tests', 'clean build directory', or 'deploy application'.
They are the building blocks that make up your entire build process.

Discovering Built-in Tasks

Gradle comes with many built-in tasks. You can list all available tasks for your project using the command line:

gradle tasks

This command shows a categorized list of tasks, including those provided by plugins and any custom tasks you define. It's a great way to explore what your build can do!

Defining Your First Task

Creating your own custom task is straightforward in your build.gradle file. Let's define a simple task:

The task keyword is used, followed by the task's name. The curly braces {} define the task's actions.

task helloWorld {
    println "Hello from CoddyKit Gradle!"
}

Running Custom Tasks

To execute a custom task, you simply run Gradle from your terminal, specifying the task name:

gradle helloWorld

When you run the example from the previous scene, you'll see "Hello from CoddyKit Gradle!" printed in the console.

Task Actions: doLast & doFirst

Tasks can have multiple actions. You can define these actions using doLast and doFirst blocks.

doLast: Adds an action to be executed at the end of the task.
doFirst: Adds an action to be executed at the beginning of the task.

These are useful for organizing complex task logic.

task myGreet {
    doFirst {
        println "Preparing to greet..."
    }
    doLast {
        println "Hello, CoddyKit!"
    }
}

Chaining Tasks with dependsOn

Often, one task must complete before another can start. Gradle handles this with task dependencies using the dependsOn keyword.

If task 'B' depends on task 'A', then 'A' will always run before 'B'. This ensures operations happen in the correct order.

task prepare {
    doLast {
        println "Preparation complete."
    }
}

task build(dependsOn: prepare) {
    doLast {
        println "Build finished."
    }
}

Understanding the Build Lifecycle

Every time you run a Gradle command, it goes through a distinct build lifecycle, consisting of three main phases:

Initialization: Sets up the build environment.
Configuration: Evaluates build scripts and configures tasks.
Execution: Runs the configured tasks.

Understanding these phases is key to writing effective Gradle builds.

Phase 1: Initialization

The Initialization Phase is where Gradle determines which projects are participating in the build.

It evaluates the settings.gradle file (if present).
This file defines the project hierarchy for multi-project builds.
Gradle creates a Project instance for each project involved.

This phase essentially sets the stage for the build.

Phase 2: Configuration

During the Configuration Phase, all build.gradle scripts for the projects are evaluated.

Tasks are created and configured.
Important: Any code directly in a task block (not inside doLast or doFirst) runs during this phase, regardless of whether the task will actually be executed.

This is where tasks' properties and dependencies are set up.

task configExample {
    println "This message runs during Configuration!"
    doLast {
        println "This message runs during Execution!"
    }
}

Phase 3: Execution

The final phase is the Execution Phase. This is where the actual work happens!

Gradle determines which tasks need to run based on your command and task dependencies.
It then executes the doFirst and doLast actions (and any other actions) of those selected tasks.
Tasks are executed in the correct order, respecting their dependencies.

This is when your code compiles, tests run, and artifacts are built.

Lifecycle Check

Let's test your understanding of Gradle's build lifecycle!

Tasks & Lifecycle Recap

Great job! You've learned the core concepts of Gradle tasks and the build lifecycle:

Tasks are the fundamental units of work.
You can define custom tasks and chain them with dependsOn.
The Gradle build proceeds through three phases: Initialization, Configuration, and Execution.
Code directly in a task block runs during Configuration, while doFirst/doLast actions run during Execution.

Next, we'll explore how Gradle manages external dependencies!

常见问题解答

「任务与构建生命周期」课时是免费的吗？

是的 — 「任务与构建生命周期」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 Groovy & Gradle: JVM Automation and Build Engineering 课程的其余内容，请升级到 CoddyKit PRO。 Groovy & Gradle: JVM Automation and Build Engineering 课程共包含 4 节课。

「任务与构建生命周期」这节课中我会学到什么？

定义和管理 Gradle 任务，了解任务依赖关系，并掌握构建生命周期的各个阶段。你通过在浏览器中直接运行的动手代码来练习 Groovy & Gradle: JVM Automation and Build Engineering，全天候 AI 导师会在你学习这节课的过程中回答你的问题。

学习 Groovy & Gradle: JVM Automation and Build Engineering 需要有经验吗？

无需任何先前经验。CoddyKit 上的 Groovy & Gradle: JVM Automation and Build Engineering 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。这是第 3 节课，共 4 节。

「任务与构建生命周期」课时需要多长时间？

大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。

我能在这节 Groovy & Gradle: JVM Automation and Build Engineering 课中编写并运行代码吗？

能。每节 Groovy & Gradle: JVM Automation and Build Engineering 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。

此课程中的所有课时

← 返回 Groovy & Gradle: JVM Automation and Build Engineering