BuildProgressCrossVersionSpec.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Change build progress tapi tests to get WorkerExecutor from task services

    • -2
    • +2
    ./BuildProgressCrossVersionSpec.groovy
  1. … 1 more file in changeset.
Add missing `KOTLIN_SCRIPT` requirement to test

    • -1
    • +1
    ./BuildProgressCrossVersionSpec.groovy
Split TAPI tests to dedicated source sets

    • -472
    • +0
    ./BuildProgressCrossVersionSpec.groovy
  1. … 346 more files in changeset.
Fixed test for changes to artifact resolution build operations.

    • -3
    • +4
    ./BuildProgressCrossVersionSpec.groovy
Fixed test for changes to build operation name.

    • -7
    • +7
    ./BuildProgressCrossVersionSpec.groovy
  1. … 1 more file in changeset.
Some test fixes for changes to display names.

    • -3
    • +3
    ./BuildProgressCrossVersionSpec.groovy
  1. … 3 more files in changeset.
Basic support for no-isolation workers

    • -2
    • +2
    ./BuildProgressCrossVersionSpec.groovy
  1. … 15 more files in changeset.
Fix TAPI tests

    • -5
    • +5
    ./BuildProgressCrossVersionSpec.groovy
  1. … 1 more file in changeset.
Unify BuildOperationExecutor and BuildOperationProcessor APIs

This introduces the following `BuildOperationExecutor`

interface (as outlined in gradle/gradle#1676):

void run(RunnableBuildOperation buildOperation);

<T> T call(CallableBuildOperation<T> buildOperation);

<O extends RunnableBuildOperation> void runAll(

Action<BuildOperationQueue<O>> schedulingAction);

<O extends BuildOperation> void runAll(

BuildOperationWorker<O> worker,

Action<BuildOperationQueue<O>> schedulingAction);

To accomplish this, the following changes were performed:

- Various representation of build operations have been merged into

1) BuildOperation (with sub-interfaces)

-> declare and describe a build operation

2) BuildOperationDescriptor (BuildOperationDescriptor.Builder)

-> describe a build operation

3) BuildOperationState

-> represents a running build operation, with run state, start time,

parent relationship information, and description

- The DefaultBuildOperationExecutor and DefaultBuildOperationProcessor

implementations have been merged in DefaultBuildOperationExecutor,

which is now build session scoped.

    • -3
    • +1
    ./BuildProgressCrossVersionSpec.groovy
  1. … 180 more files in changeset.
Build operation name `resolve dependencies` -> `resolve dependencies of`

    • -3
    • +3
    ./BuildProgressCrossVersionSpec.groovy
  1. … 6 more files in changeset.
Name of build operation `resolve artifacts` -> `resolve artifacts of`

    • -3
    • +3
    ./BuildProgressCrossVersionSpec.groovy
  1. … 2 more files in changeset.
Improve naming of build operations: adjust test expectations

    • -32
    • +49
    ./BuildProgressCrossVersionSpec.groovy
  1. … 1 more file in changeset.
Change tooling API test target versions from 3.6 to 4.0

    • -0
    • +456
    ./BuildProgressCrossVersionSpec.groovy
  1. … 5 more files in changeset.
Add build operation for resolving all artifacts

This generates a "resolve artifacts" build operation if

getFiles() is called on lenient configuration.

    • -9
    • +10
    ./BuildProgressCrossVersionSpec.groovy
  1. … 5 more files in changeset.
Fix r36/BuildProgressCrossVersionSpec after bad rebase/merge

    • -0
    • +1
    ./BuildProgressCrossVersionSpec.groovy
Worker lease and build operation for the whole build execution

DefaultGradleLauncher now holds a worker lease around the whole build

execution. This will allow for worker lease management at configuration

time.

It now also emits a ‘Run build’ build operation around the whole build

execution. Previously it was only emitted when executing a build through

TAPI.

    • -2
    • +0
    ./BuildProgressCrossVersionSpec.groovy
  1. … 8 more files in changeset.