GradleBuildTaskIntegrationTest.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.

    • -0
    • +42
    ./GradleBuildTaskIntegrationTest.groovy
  1. … 72 more files in changeset.
Synchronize access to build state registry in GradleBuild

    • -0
    • +1
    ./GradleBuildTaskIntegrationTest.groovy
  1. … 1 more file in changeset.
Ensure build paths are unique before using them

Also pushes uniqueness validation earlier

    • -0
    • +41
    ./GradleBuildTaskIntegrationTest.groovy
  1. … 7 more files in changeset.
Revert "Merge pull request #10795 from gradle/lacasseio/deprecate-methods-on-start-parameter"

This reverts commit 40cb80789fed1f36e5501d9e8ac35fcb290c6b76, reversing

changes made to f6c349254943c709e33dd409729174f5adf9f6ce.

    • -29
    • +0
    ./GradleBuildTaskIntegrationTest.groovy
  1. … 9 more files in changeset.
Warn about deprecation of search upwards and similar APIs

    • -0
    • +29
    ./GradleBuildTaskIntegrationTest.groovy
  1. … 9 more files in changeset.
Change a few tests to use the various assertion methods to verify that a `buildSrc` task runs, rather than scraping the logging output.

    • -5
    • +3
    ./GradleBuildTaskIntegrationTest.groovy
  1. … 2 more files in changeset.
Change a few tests to use the various assertion methods to verify that a `buildSrc` task runs, rather than scraping the logging output.

    • -5
    • +3
    ./GradleBuildTaskIntegrationTest.groovy
  1. … 2 more files in changeset.
Change a few tests to use the various assertion methods to verify that a `buildSrc` task runs, rather than scraping the logging output.

    • -5
    • +3
    ./GradleBuildTaskIntegrationTest.groovy
  1. … 2 more files in changeset.
Change a few tests to use the various assertion methods to verify that a `buildSrc` task runs, rather than scraping the logging output.

    • -5
    • +3
    ./GradleBuildTaskIntegrationTest.groovy
  1. … 2 more files in changeset.
Change a few tests to use the various assertion methods to verify that a `buildSrc` task runs, rather than scraping the logging output.

    • -5
    • +3
    ./GradleBuildTaskIntegrationTest.groovy
  1. … 2 more files in changeset.
Change a few tests to use the various assertion methods to verify that a `buildSrc` task runs, rather than scraping the logging output.

    • -5
    • +3
    ./GradleBuildTaskIntegrationTest.groovy
  1. … 2 more files in changeset.
Change a few tests to use the various assertion methods to verify that a `buildSrc` task runs, rather than scraping the logging output.

    • -5
    • +3
    ./GradleBuildTaskIntegrationTest.groovy
  1. … 2 more files in changeset.
Add settings file where required for integ tests

    • -0
    • +3
    ./GradleBuildTaskIntegrationTest.groovy
  1. … 8 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.

    • -5
    • +4
    ./GradleBuildTaskIntegrationTest.groovy
  1. … 6 more files in changeset.
Register the projects of a build run using `GradleBuild` so they are visible to dependency resolution and other things that use the `ProjectStateRegistry` infrastructure, such as the IDE plugins.

    • -0
    • +78
    ./GradleBuildTaskIntegrationTest.groovy
  1. … 10 more files in changeset.
Include GradleBuild task build operations in the build operation tree (#4560).

This is the conceptual intent. Furthermore, it's necessary for build operation notification based log output which will be required for scans.

    • -1
    • +11
    ./GradleBuildTaskIntegrationTest.groovy
  1. … 26 more files in changeset.
Tweaked the API of `BlockingHttpServer` to make it somewhat more convenient to use in tests.

    • -2
    • +2
    ./GradleBuildTaskIntegrationTest.groovy
  1. … 15 more files in changeset.
Some fixes for timeout in int test: switched to using Java for unit tests in the test build, and compile everything prior to starting the test build.

    • -4
    • +4
    ./GradleBuildTaskIntegrationTest.groovy
  1. … 8 more files in changeset.
Use fewer parallel builds for int test.

    • -3
    • +3
    ./GradleBuildTaskIntegrationTest.groovy
Fixes to tracking of parent build for builds started using `GradleBuild` task, when multiple `GradleBuild` tasks are running concurrently.

    • -0
    • +61
    ./GradleBuildTaskIntegrationTest.groovy
  1. … 4 more files 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.

    • -0
    • +21
    ./GradleBuildTaskIntegrationTest.groovy
  1. … 23 more files in changeset.
Added some more test coverage for `GradleBuild` task type.

    • -0
    • +63
    ./GradleBuildTaskIntegrationTest.groovy
  1. … 1 more file in changeset.