IncrementalBuildIntegrationTest.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Make paths/names of included builds immutable (#10998)

Changes the “build path” for included builds to be determined at inclusion time based on the directory name, or a user supplied override. Previously, we tried to use the root project name defined in the included build. This caused a lot of complexity due to it not being known until part way through building the included build.

This change also disallows use of `buildSrc` as a project name, as it collides with the `buildSrc` nested build.

    • -2
    • +2
    ./IncrementalBuildIntegrationTest.groovy
  1. … 72 more files in changeset.
Fix tests

    • -2
    • +2
    ./IncrementalBuildIntegrationTest.groovy
Revert test changes

The changes are only needed when fine-grained invalidation is enabled.

    • -4
    • +0
    ./IncrementalBuildIntegrationTest.groovy
Revert test changes

The changes are only needed when fine-grained invalidation is enabled.

    • -4
    • +0
    ./IncrementalBuildIntegrationTest.groovy
Revert test changes

The changes are only needed when fine-grained invalidation is enabled.

    • -4
    • +0
    ./IncrementalBuildIntegrationTest.groovy
Fix test by declaring outputs

    • -0
    • +4
    ./IncrementalBuildIntegrationTest.groovy
Fix test by declaring outputs

    • -0
    • +4
    ./IncrementalBuildIntegrationTest.groovy
Fix test by declaring outputs

    • -0
    • +4
    ./IncrementalBuildIntegrationTest.groovy
Fix test by declaring outputs

    • -0
    • +4
    ./IncrementalBuildIntegrationTest.groovy
Fix test by declaring outputs

    • -0
    • +4
    ./IncrementalBuildIntegrationTest.groovy
Fix IncrementalBuildIntegrationTest

    • -0
    • +9
    ./IncrementalBuildIntegrationTest.groovy
Fix test

    • -1
    • +1
    ./IncrementalBuildIntegrationTest.groovy
Address review feedback

    • -4
    • +1
    ./IncrementalBuildIntegrationTest.groovy
  1. … 4 more files in changeset.
Address review feedback

    • -3
    • +1
    ./IncrementalBuildIntegrationTest.groovy
  1. … 5 more files in changeset.
Address review feedback

    • -4
    • +1
    ./IncrementalBuildIntegrationTest.groovy
  1. … 5 more files in changeset.
Deprecate declaring incremental tasks with no outputs

An incremental task should always declare an output. Gradle

automatically declared an upToDate spec for incremental tasks to make

sure this is always the case.

Actually, the implementor of the task should add the spec if the task

does not declare any outputs. We expect nearly all incremental tasks

to already declare outputs.

#9723

    • -0
    • +3
    ./IncrementalBuildIntegrationTest.groovy
  1. … 7 more files in changeset.
Deprecate declaring incremental tasks with no outputs

An incremental task should always declare an output. Gradle

automatically declared an upToDate spec for incremental tasks to make

sure this is always the case.

Actually, the implementor of the task should add the spec if the task

does not declare any outputs. We expect nearly all incremental tasks

to already declare outputs.

    • -0
    • +3
    ./IncrementalBuildIntegrationTest.groovy
  1. … 7 more files in changeset.
Deprecate declaring incremental tasks with no outputs

An incremental task should always declare an output. Gradle

automatically declared an upToDate spec for incremental tasks to make

sure this is always the case.

Actually, the implementor of the task should add the spec if the task

does not declare any outputs. We expect nearly all incremental tasks

to already declare outputs.

#9723

    • -0
    • +3
    ./IncrementalBuildIntegrationTest.groovy
  1. … 7 more files in changeset.
Change more tests.

    • -1
    • +1
    ./IncrementalBuildIntegrationTest.groovy
  1. … 40 more files in changeset.
Change more tests.

    • -4
    • +4
    ./IncrementalBuildIntegrationTest.groovy
  1. … 17 more files in changeset.
Change more tests.

    • -1
    • +1
    ./IncrementalBuildIntegrationTest.groovy
  1. … 13 more files in changeset.
Changed a bunch of integration tests to use the various task assertion methods instead of directly querying the `executedTasks` and `skippedTasks` collections. These methods can give better diagnostics when the assertion fails, and can perform additional checks.

    • -6
    • +6
    ./IncrementalBuildIntegrationTest.groovy
  1. … 98 more files in changeset.
Changed a bunch of integration tests to use the various task assertion methods instead of directly querying the `executedTasks` and `skippedTasks` collections. These methods can give better diagnostics when the assertion fails, and can perform additional checks.

    • -6
    • +6
    ./IncrementalBuildIntegrationTest.groovy
  1. … 98 more files in changeset.
Changed a bunch of integration tests to use the various task assertion methods instead of directly querying the `executedTasks` and `skippedTasks` collections. These methods can give better diagnostics when the assertion fails, and can perform additional checks.

    • -6
    • +6
    ./IncrementalBuildIntegrationTest.groovy
  1. … 98 more files in changeset.
Use `_Decorated` as class name for generated task classes

If we don't, there seems to be some problems when syncing with IDEA.

See #8244

    • -1
    • +1
    ./IncrementalBuildIntegrationTest.groovy
  1. … 3 more files in changeset.
Allow the services required by a given class to be queried prior to creating any instances of that class. Use this to allow `ArtifactTransformDependencies` to be injected into artifact transforms using any of the service injection patterns (that is, via a constructor or a getter).

    • -1
    • +1
    ./IncrementalBuildIntegrationTest.groovy
  1. … 127 more files in changeset.
Unwrap implementations when comparing for changes

    • -2
    • +2
    ./IncrementalBuildIntegrationTest.groovy
  1. … 4 more files in changeset.
Move change detection to execution project

    • -2
    • +2
    ./IncrementalBuildIntegrationTest.groovy
  1. … 65 more files in changeset.
Avoid use of `startParameter.searchUpwards` in tests

When `GradleBuild` tasks were used in integration tests, we were often

resorting to `startParameter.searchUpwards = false` to target an isolated

build script. Instead, use an explicitly defined `settings.gradle` in each target

build.

    • -1
    • +0
    ./IncrementalBuildIntegrationTest.groovy
  1. … 6 more files in changeset.
Non-directory fileTrees can now be used as outputs

    • -35
    • +1
    ./IncrementalBuildIntegrationTest.groovy