BuildProgressCrossVersionSpec.groovy

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

    • -1
    • +1
    ./BuildProgressCrossVersionSpec.groovy
  1. … 1 more file in changeset.
Fixes for running TAPI int test against Gradle 2.5.

    • -3
    • +3
    ./BuildProgressCrossVersionSpec.groovy
Fixed version range on tapi int test.

    • -0
    • +2
    ./BuildProgressCrossVersionSpec.groovy
Some tweaks to display names in tapi build progress events from nested builds.

    • -24
    • +31
    ./BuildProgressCrossVersionSpec.groovy
  1. … 14 more files in changeset.
Added more test coverage for tapi build progress events from nested builds.

    • -21
    • +84
    ./BuildProgressCrossVersionSpec.groovy
  1. … 1 more file in changeset.
Added some test coverage for tapi build progress events.

    • -8
    • +36
    ./BuildProgressCrossVersionSpec.groovy
  1. … 3 more files in changeset.
Changed the wiring of the listeners that forward events back to the tapi client so that they received events from _all_ builds, not just the root build. This in particular means that progress events are received from `buildSrc` builds, composite builds, and builds started using the `GradleBuild` task.

Cleaned up `BuildScopeServices` so that it is no longer responsible for cleaning up its parent.

    • -0
    • +36
    ./BuildProgressCrossVersionSpec.groovy
  1. … 7 more files in changeset.
Ensure that task and project configuration failures are attached to TAPI progress events.

Reworked `BuildOperationExecutor` to allow the action for an operation to mark the operation as failed without throwing an exception.

    • -5
    • +118
    ./BuildProgressCrossVersionSpec.groovy
  1. … 19 more files in changeset.
Treat resolution of a dependency graph as a build operation, to make it visible to instrumentation. This means, for example, that resolution of each configuration will be visible to TAPI clients using `ProgressListener`.

    • -6
    • +118
    ./BuildProgressCrossVersionSpec.groovy
  1. … 8 more files in changeset.
Treat configuration of a project as a build operation, to make it visible to instrumentation. This means, for example, that configuration of each project will be visible to TAPI clients using `ProgressListener`.

    • -0
    • +65
    ./BuildProgressCrossVersionSpec.groovy
  1. … 3 more files in changeset.