PhasedActionEventConsumerTest.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Inline org.gradle.testing.internal.util.Specification

    • -1
    • +1
    ./PhasedActionEventConsumerTest.groovy
  1. … 53 more files in changeset.
Inline org.gradle.testing.internal.util.Specification

    • -1
    • +1
    ./PhasedActionEventConsumerTest.groovy
  1. … 53 more files in changeset.
Inline org.gradle.testing.internal.util.Specification

    • -1
    • +1
    ./PhasedActionEventConsumerTest.groovy
  1. … 52 more files in changeset.
Inline org.gradle.testing.internal.util.Specification

    • -1
    • +1
    ./PhasedActionEventConsumerTest.groovy
  1. … 53 more files in changeset.
Remove projectsEvaluated hook from PhasedActions

And modify projectsLoaded hook to be run after configuration, making

sure that requested models are available.

For now, projects are configurated completely before running the

projectsLoaded action, however we can try to avoid unnecessary

configuration in the future without modifying public APIs.

Signed-off-by: Lucas Smaira <lsmaira@google.com>

    • -10
    • +2
    ./PhasedActionEventConsumerTest.groovy
  1. … 19 more files in changeset.
Code and documentation ajustments to PR

This commit:

- Renames methods in PhasedBuildActionExecuter and corresponding uses

- Improves public java docs making them more precise

- Replaces mocks by stubs in unit tests when possible

- Makes action's handlers in phased actions not receiving failures (they

are send to build results)

Signed-off-by: Lucas Smaira <lsmaira@google.com>

    • -52
    • +12
    ./PhasedActionEventConsumerTest.groovy
  1. … 38 more files in changeset.
Introduce support for running phased actions

This commit introduces the ability of running multiple build actions in

different phases of the build. These actions are passed by the client

through the tooling api.

With this commit, a single action can be added to each one of the

supporting phases (after projects are loaded, after projects are

evaluated and after tasks are run).

This feature allows improvements like running actions that call a model

builder modifying the graph tasks, and then it is possible to first

fetch a model and then execute tasks, in this order. e.g. Android Studio

sync + source generation.

Signed-off-by: Lucas Smaira <lsmaira@google.com>

    • -0
    • +117
    ./PhasedActionEventConsumerTest.groovy
  1. … 54 more files in changeset.