DependencyDownloadBuildOperationsIntegrationTest.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Introduce -Dorg.gradle.operations.trace=«path» mechanism for logging operations of any build.

    • -5
    • +3
    ./DependencyDownloadBuildOperationsIntegrationTest.groovy
  1. … 14 more files in changeset.
Reorganise the rich build operation details/results type to further decouple from producer side semantics.

    • -4
    • +4
    ./DependencyDownloadBuildOperationsIntegrationTest.groovy
  1. … 82 more files in changeset.
Spike of decoupled build operation listening.

    • -9
    • +5
    ./DependencyDownloadBuildOperationsIntegrationTest.groovy
  1. … 7 more files in changeset.
Use BuildOperationsFixture in DependencyDownloadBuildOperationsIntegrationTest

see https://github.com/gradle/gradle/pull/1907

    • -22
    • +15
    ./DependencyDownloadBuildOperationsIntegrationTest.groovy
  1. … 1 more file in changeset.
Fix test after merge

    • -2
    • +2
    ./DependencyDownloadBuildOperationsIntegrationTest.groovy
Fix test

    • -2
    • +3
    ./DependencyDownloadBuildOperationsIntegrationTest.groovy
Obtain the expected size from the actual file.

    • -2
    • +2
    ./DependencyDownloadBuildOperationsIntegrationTest.groovy
Adapt DownloadBuildOperationDetails to latest BuildOperationDetails refactorings

    • -5
    • +5
    ./DependencyDownloadBuildOperationsIntegrationTest.groovy
  1. … 4 more files in changeset.
Convey the number of content bytes read in the download build operation result.

This provides a more (but not absolutely) reliable indicator of bytes transferred than the advertised content length pre transfer.

    • -0
    • +85
    ./DependencyDownloadBuildOperationsIntegrationTest.groovy
  1. … 12 more files in changeset.