EvaluateSettingsBuildOperationIntegrationTest.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Publish Gradle Module Metadata by default

    • -1
    • +1
    ./EvaluateSettingsBuildOperationIntegrationTest.groovy
  1. … 4 more files in changeset.
Publish Gradle Module Metadata by default

    • -1
    • +1
    ./EvaluateSettingsBuildOperationIntegrationTest.groovy
  1. … 4 more files in changeset.
Publish Gradle Module Metadata by default

    • -1
    • +1
    ./EvaluateSettingsBuildOperationIntegrationTest.groovy
  1. … 4 more files in changeset.
Publish Gradle Module Metadata by default

    • -1
    • +1
    ./EvaluateSettingsBuildOperationIntegrationTest.groovy
  1. … 4 more files in changeset.
Removed `GradleExecuter.withSearchUpwards()`

Search-upwards is now the default behaviour, and we ensure that a

settings file is available for all integration tests.

    • -1
    • +0
    ./EvaluateSettingsBuildOperationIntegrationTest.groovy
  1. … 3 more files in changeset.
Remove unused improve pom support flags

    • -1
    • +1
    ./EvaluateSettingsBuildOperationIntegrationTest.groovy
  1. … 19 more files in changeset.
Move the introduced API to Settings

This limits its applicability to settings.gradle and makes it clearer

about the scope.

See #4086 for discussions on this.

    • -0
    • +9
    ./EvaluateSettingsBuildOperationIntegrationTest.groovy
  1. … 10 more files in changeset.
Implement a workaround to make build operation traces fully functional for composite builds. (#4227)

Relates to #3873.

    • -3
    • +4
    ./EvaluateSettingsBuildOperationIntegrationTest.groovy
  1. … 11 more files in changeset.
More cleanup on new build operation implementation and test coverage

    • -4
    • +4
    ./EvaluateSettingsBuildOperationIntegrationTest.groovy
  1. … 1 more file in changeset.
summarize func tests for new build operations

- due to https://github.com/gradle/gradle/issues/3873 we only check buildpath for root builds.

- BuildOperationNotificationsFixture ensures the scan plugin use case is covered and buildpath can be consumed from build scan plugin

    • -0
    • +4
    ./EvaluateSettingsBuildOperationIntegrationTest.groovy
  1. … 2 more files in changeset.
Simplify integration tests

    • -12
    • +15
    ./EvaluateSettingsBuildOperationIntegrationTest.groovy
  1. … 1 more file in changeset.
Renamed `ConfigureSettings` build operation to `EvaluateSettings`

    • -0
    • +111
    ./EvaluateSettingsBuildOperationIntegrationTest.groovy
  1. … 4 more files in changeset.