BuildOperationNotificationIntegrationTest.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Fix test

    • -9
    • +23
    ./BuildOperationNotificationIntegrationTest.groovy
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.

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

    • -1
    • +1
    ./BuildOperationNotificationIntegrationTest.groovy
Fix some tests.

    • -1
    • +1
    ./BuildOperationNotificationIntegrationTest.groovy
  1. … 1 more file 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.

    • -1
    • +1
    ./BuildOperationNotificationIntegrationTest.groovy
  1. … 50 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.

    • -1
    • +1
    ./BuildOperationNotificationIntegrationTest.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.

    • -1
    • +1
    ./BuildOperationNotificationIntegrationTest.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.

    • -1
    • +1
    ./BuildOperationNotificationIntegrationTest.groovy
  1. … 50 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.

    • -1
    • +1
    ./BuildOperationNotificationIntegrationTest.groovy
  1. … 98 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.

    • -1
    • +1
    ./BuildOperationNotificationIntegrationTest.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.

    • -1
    • +1
    ./BuildOperationNotificationIntegrationTest.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.

    • -1
    • +1
    ./BuildOperationNotificationIntegrationTest.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.

    • -1
    • +1
    ./BuildOperationNotificationIntegrationTest.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.

    • -1
    • +1
    ./BuildOperationNotificationIntegrationTest.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.

    • -1
    • +1
    ./BuildOperationNotificationIntegrationTest.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.

    • -1
    • +1
    ./BuildOperationNotificationIntegrationTest.groovy
  1. … 2 more files in changeset.
Return some incremental execution results in an immutable way

We now use TaskExecuterResult instead of TaskExecutionContext.

    • -1
    • +1
    ./BuildOperationNotificationIntegrationTest.groovy
  1. … 16 more files in changeset.
Synchronize test operation notification listener

Also includes some diagnostic improvements

    • -1
    • +0
    ./BuildOperationNotificationIntegrationTest.groovy
  1. … 2 more files in changeset.
Move ExecuteTaskBuildOperationType (#7374)

* Move ExecuteTaskBuildOperationType to org.gradle.api.internal.tasks.execution

* Remove redundant import

    • -1
    • +1
    ./BuildOperationNotificationIntegrationTest.groovy
  1. … 25 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.

    • -2
    • +1
    ./BuildOperationNotificationIntegrationTest.groovy
  1. … 6 more files in changeset.
Simplify BuildOperationNotificationListenerRegistrar

Only keep the method used by build scan plugin 2.0, which is the minimum

version required for Gradle 5.0+.

    • -29
    • +4
    ./BuildOperationNotificationIntegrationTest.groovy
  1. … 9 more files in changeset.
Expose which build included the build being loaded to operation listeners (#6181)

* Record which build included the build and expose in LoadBuild operation

    • -7
    • +5
    ./BuildOperationNotificationIntegrationTest.groovy
  1. … 26 more files in changeset.
Refine test API

    • -4
    • +4
    ./BuildOperationNotificationIntegrationTest.groovy
  1. … 1 more file in changeset.
Fix tests, mark more internal listeners

    • -3
    • +4
    ./BuildOperationNotificationIntegrationTest.groovy
  1. … 22 more files in changeset.
Emit build operation for executing taskgraph whenReady hooks (#5647)

Emit build operation for executing taskgraph whenReady hooks

    • -0
    • +12
    ./BuildOperationNotificationIntegrationTest.groovy
  1. … 5 more files in changeset.
Add build operations around after/beforeEvaluate and projectsLoaded/Evaluated lifecycle hooks (#5558)

* Wrap build op around projectsLoaded hooks

Signed-off-by: Tom Dunstan <tom@gradle.com>

* Add test coverage

Signed-off-by: Tom Dunstan <tom@gradle.com>

* Wrap build op around projectsEvaluated hooks

Signed-off-by: Tom Dunstan <tom@gradle.com>

* Wrap build ops around project evaluation hooks

Signed-off-by: Tom Dunstan <tom@gradle.com>

* Don't make new ops logging groups

Signed-off-by: Tom Dunstan <tom@gradle.com>

* Add test coverage

Signed-off-by: Tom Dunstan <tom@gradle.com>

* Quieten down logging

Signed-off-by: Tom Dunstan <tom@gradle.com>

* Fix test

Signed-off-by: Tom Dunstan <tom@gradle.com>

* Fix codenarc

Signed-off-by: Tom Dunstan <tom@gradle.com>

* Polish before and after evaluate build operations

* Polish projectsEvaluated and projectsLoaded build operations

* fix unit tests

* Use wrapped exception as operation failure exception

    • -4
    • +52
    ./BuildOperationNotificationIntegrationTest.groovy
  1. … 19 more files in changeset.
Allow a build operation notification listeners during continuous build (#5453)

This accidentally worked < 4.7. In 4.7 the notification bridge became cross session scoped in order to support bridging the logging output to progress notifications. This broke what was accidentally working, by retaining the notification listener across builds of a continuous build.

This change restores the accidental support by explicitly clearing the bridge state after each build of a continuous build, allowing a new listener on the subsequent build.

    • -206
    • +83
    ./BuildOperationNotificationIntegrationTest.groovy
  1. … 12 more files in changeset.
Split loading and configuring of included builds, so that included builds are loaded during the loading of the root build and configured during configuration of the root build (if required). Previously, included builds were loaded and also configured during loading (if required). This better allocates the work between the relevant top level build operation and also allows further laziness in configuring of included builds to be added later.

    • -2
    • +2
    ./BuildOperationNotificationIntegrationTest.groovy
  1. … 13 more files in changeset.
Emit build operation progress events for logging output (#4537)

* Tweak BuildOperationListener#progress api

* Use build operation id to reference progress

* Add workaround for tracing log output via build operation progress for composite builds

* Replace some Object typing of operation identifiers with OperationIdentifier.

* Associate all progress logging with the current build operation.

* Update logic to accommodate for all progress events now having build operation IDs.

* Don't allow ProgressStartEvent.buildOperationCategory to be null.

** Default it to uncategorized.

    • -4
    • +5
    ./BuildOperationNotificationIntegrationTest.groovy
  1. … 50 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.

    • -9
    • +22
    ./BuildOperationNotificationIntegrationTest.groovy
  1. … 26 more files in changeset.