CompositeBuildTaskDependencyIntegrationTest.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Rename @FailsWithInstantExecution to @ToBeFixedForInstantExecution

Signed-off-by: Paul Merlin <paul@gradle.com>

    • -8
    • +8
    ./CompositeBuildTaskDependencyIntegrationTest.groovy
  1. … 872 more files in changeset.
Annotate integ tests failing with instant execution in :compositeBuilds

Signed-off-by: Paul Merlin <paul@gradle.com>

    • -0
    • +8
    ./CompositeBuildTaskDependencyIntegrationTest.groovy
  1. … 27 more files in changeset.
Annotate integ tests failing with instant execution in :compositeBuilds

Signed-off-by: Paul Merlin <paul@gradle.com>

    • -0
    • +8
    ./CompositeBuildTaskDependencyIntegrationTest.groovy
  1. … 27 more files in changeset.
Annotate integ tests failing with instant execution in :compositeBuilds

Signed-off-by: Paul Merlin <paul@gradle.com>

    • -0
    • +8
    ./CompositeBuildTaskDependencyIntegrationTest.groovy
  1. … 27 more files in changeset.
Let composite-build tests not use deprecated configurations

    • -1
    • +1
    ./CompositeBuildTaskDependencyIntegrationTest.groovy
  1. … 12 more files in changeset.
Let composite-build tests not use deprecated configurations

    • -1
    • +1
    ./CompositeBuildTaskDependencyIntegrationTest.groovy
  1. … 12 more files in changeset.
Let composite-build tests not use deprecated configurations

    • -1
    • +1
    ./CompositeBuildTaskDependencyIntegrationTest.groovy
  1. … 12 more files in changeset.
Use java-library and its configurations in ResolveTestFixture

This mainly influences the composite build tests which intensively

use this fixture.

    • -1
    • +1
    ./CompositeBuildTaskDependencyIntegrationTest.groovy
  1. … 13 more files in changeset.
Add some more test coverage to verify the IDE plugins are consistent in how they behave in composite builds. This just covers a couple of simple scenarios.

Change the `eclipse` task of the root project so that it generates the Eclipse projects for all builds, and so produces usable project files when there are included builds.

    • -3
    • +3
    ./CompositeBuildTaskDependencyIntegrationTest.groovy
  1. … 19 more files in changeset.
Expose file collection dependencies declared in included builds to consumers in other builds in the composite.

Rework task graph assembly so that tasks that cross build boundaries as a dependency of another task no longer need to be wrapped in a `TaskReference` and remove the special handling from dependency resolution artifact and IDE artifact implementations.

No longer add a synthetic delegate task to each project that such a task is consumed as a dependency and decouple the task execution plan from `Task` slightly so that it can deal with the difference between tasks in the current build and tasks running asynchronously in another build.

    • -20
    • +6
    ./CompositeBuildTaskDependencyIntegrationTest.groovy
  1. … 24 more files in changeset.
Ensure exact task name is supplied for included build task reference

We were incidentally permitting the shorthand notation when creating an

included build task reference. With recent changes, this no longer works

because the task requested doesn't match the task executed.

This commit removes the ability to provide a partially-matched task

name for an included build task reference.

This also fixes an integration test that accidentally relied on partial-name

matching, thus exposing the changed behaviour.

    • -0
    • +24
    ./CompositeBuildTaskDependencyIntegrationTest.groovy
  1. … 2 more files in changeset.
Use a separate delegating task reference per task per included build

    • -2
    • +2
    ./CompositeBuildTaskDependencyIntegrationTest.groovy
  1. … 5 more files in changeset.
Don't wrap exceptions from included builds

    • -2
    • +1
    ./CompositeBuildTaskDependencyIntegrationTest.groovy
  1. … 6 more files in changeset.
Improve exception message for included build task failure

    • -2
    • +1
    ./CompositeBuildTaskDependencyIntegrationTest.groovy
  1. … 4 more files in changeset.
Tighten up test coverage

By using task references for included build artifacts, we can now

assert ordering that wasn't possible before.

    • -1
    • +3
    ./CompositeBuildTaskDependencyIntegrationTest.groovy
  1. … 1 more file in changeset.
More consistently include the build identity to the display name for projects and tasks used in various places such as error messages, logging output and tapi progress events.

Added `identityPath` property (for want of a better name) to internal `Gradle`, `Project` and `Task` types for now to allow this to be queried. This path always includes the build identity, and is used to calculate the display name.

Added a bunch of coverage for using `buildSrc` in various nested builds.

    • -2
    • +2
    ./CompositeBuildTaskDependencyIntegrationTest.groovy
  1. … 23 more files in changeset.
Use doLast instead of left shift operator

Made this change in preparation for deprecating the left shift operator.

+review REVIEW-6236

    • -2
    • +4
    ./CompositeBuildTaskDependencyIntegrationTest.groovy
  1. … 163 more files in changeset.
Removed extra validation that is of dubious value

Since this validation error always appears in the context of the

build being configured, providing this additional detail is probably

not worth it.

+review REVIEW-6192

    • -2
    • +2
    ./CompositeBuildTaskDependencyIntegrationTest.groovy
  1. … 1 more file in changeset.
Test dependency substitution in included build task

+review REVIEW-6192

    • -0
    • +24
    ./CompositeBuildTaskDependencyIntegrationTest.groovy
Fail gracefully for name collision with delegating task

+review REVIEW-6192

    • -0
    • +17
    ./CompositeBuildTaskDependencyIntegrationTest.groovy
  1. … 1 more file in changeset.
Use a single delegating task for each included build

Rather than constructing a separate delegating task for each task

dependency in an included build, we now use a single delegating task

for all tasks in an included build. This means that if the task graph

contains multiple task dependencies on an included build, all of these

tasks will be run in a single build execution, at the time the first

task of them is required.

+review REVIEW-6192

    • -0
    • +55
    ./CompositeBuildTaskDependencyIntegrationTest.groovy
  1. … 2 more files in changeset.
More test coverage for included builds

- Included build with same name as composing build

- Declared substitutions for same included build

- Remove tests for explicit wiring of task delegate

    • -32
    • +0
    ./CompositeBuildTaskDependencyIntegrationTest.groovy
  1. … 3 more files in changeset.
Check that included build task path is qualified

    • -0
    • +244
    ./CompositeBuildTaskDependencyIntegrationTest.groovy
  1. … 3 more files in changeset.