BuildScanFailureMessageHintIntegrationTest.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Integrate with Gradle Enterprise plugin 3.0 (#11041)

    • -18
    • +18
    ./BuildScanFailureMessageHintIntegrationTest.groovy
  1. … 52 more files in changeset.
Update scan support for Gradle Enterprise plugin 3.0

Gradle 6 is now only compatible with this plugin.

    • -18
    • +18
    ./BuildScanFailureMessageHintIntegrationTest.groovy
  1. … 35 more files in changeset.
Stop ignoring tests and fix removed deprecated build scan property

    • -4
    • +2
    ./BuildScanFailureMessageHintIntegrationTest.groovy
  1. … 7 more files in changeset.
Ignore tests until build scan plugin 2.0 is out and used in AutoAppliedBuildScanPlugin

    • -0
    • +2
    ./BuildScanFailureMessageHintIntegrationTest.groovy
  1. … 1 more file in changeset.
Use external repository mirrors in build (#6094)

We've been bitten by external repository fluctuation for a long time.

This PR makes most of tests use repository mirrors set up by ourselves

via init script and system property.

There're still some tests not switching to mirrors, which would be fixed

in follow-up commits.

    • -3
    • +4
    ./BuildScanFailureMessageHintIntegrationTest.groovy
  1. … 99 more files in changeset.
Recover ignored tests

See https://github.com/gradle/gradle-private/issues/1341

and https://github.com/gradle/gradle/issues/5777

Recover these tests after jfrog adjusted their cipher configuration

    • -2
    • +2
    ./BuildScanFailureMessageHintIntegrationTest.groovy
  1. … 6 more files in changeset.
    • -2
    • +2
    ./BuildScanFailureMessageHintIntegrationTest.groovy
  1. … 2 more files in changeset.
Change int tests to use relevant fixture methods to express their expectations about the build log output.

    • -7
    • +7
    ./BuildScanFailureMessageHintIntegrationTest.groovy
  1. … 30 more files in changeset.
Introduce several methods on `ExecutionResult` and `ExecutionFailure` to allow a test to express various expectations about the logging output of the build, rather than scraping the `output` and `errorOutput` properties in the test.

Change several tests to use these fixture methods, plus fix several other tests for changes to the logging output.

    • -2
    • +1
    ./BuildScanFailureMessageHintIntegrationTest.groovy
  1. … 21 more files in changeset.
The error message of a failed build should render a hint to use the `--scan` command line option (#3521)

    • -0
    • +252
    ./BuildScanFailureMessageHintIntegrationTest.groovy
  1. … 6 more files in changeset.