BuildScanConfigIntegrationTest.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Rename @FailsWithInstantExecution to @ToBeFixedForInstantExecution

Signed-off-by: Paul Merlin <paul@gradle.com>

    • -14
    • +14
    ./BuildScanConfigIntegrationTest.groovy
  1. … 872 more files in changeset.
Annotate integ tests failing with instant execution in :core

Signed-off-by: Paul Merlin <paul@gradle.com>

    • -0
    • +14
    ./BuildScanConfigIntegrationTest.groovy
  1. … 99 more files in changeset.
Annotate integ tests failing with instant execution in :core

Signed-off-by: Paul Merlin <paul@gradle.com>

    • -0
    • +14
    ./BuildScanConfigIntegrationTest.groovy
  1. … 99 more files in changeset.
Annotate integ tests failing with instant execution in :core

Signed-off-by: Paul Merlin <paul@gradle.com>

    • -0
    • +14
    ./BuildScanConfigIntegrationTest.groovy
  1. … 100 more files in changeset.
Integrate with Gradle Enterprise plugin 3.0 (#11041)

    • -5
    • +5
    ./BuildScanConfigIntegrationTest.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.

    • -5
    • +5
    ./BuildScanConfigIntegrationTest.groovy
  1. … 35 more files in changeset.
Create a dedicate registration point for the scan plugin's end of build callback (#7542)

    • -0
    • +13
    ./BuildScanConfigIntegrationTest.groovy
  1. … 11 more files in changeset.
Require build scan plugin 2.0 or later for Gradle 5

    • -38
    • +1
    ./BuildScanConfigIntegrationTest.groovy
  1. … 1 more file in changeset.
Disallow build scan plugin < 1.13

Older plugins are currently broken on Gradle nightly builds.

While we still need to make a final compatibility decision on which

versions to support for 5.0, we should immediately stop anyone using

nightly builds from using unsupported versions, as they will experience

UI errors due to missing data when viewing created scans.

Intentionally not cleaning up any APIs at this point (e.g. the

attributes are no longer used) as we should do that as part of a

proper cleanup before 5.0.

    • -26
    • +1
    ./BuildScanConfigIntegrationTest.groovy
  1. … 2 more files in changeset.
Fix BuildScanPluginCompatibility after Kotlin DSL 1.0-RC3

The toggle moved from a project property to a system property

Signed-off-by: Paul Merlin <paul@gradle.com>

    • -2
    • +2
    ./BuildScanConfigIntegrationTest.groovy
  1. … 3 more files in changeset.
Disable scan plugin <= 1.15.1 if Kotlin script build caching is used (#6323)

    • -1
    • +22
    ./BuildScanConfigIntegrationTest.groovy
  1. … 3 more files in changeset.
Remove the internal support for source dependencies from a directory. Now, all source dependencies must be hosted in a Git repository, which may be local.

    • -6
    • +2
    ./BuildScanConfigIntegrationTest.groovy
  1. … 8 more files in changeset.
Allow build scans to gracefully degrade with the implicit continuous build added in 4.7 (#5369)

    • -100
    • +43
    ./BuildScanConfigIntegrationTest.groovy
  1. … 13 more files in changeset.
Remove references to old API in docs

    • -1
    • +1
    ./BuildScanConfigIntegrationTest.groovy
  1. … 2 more files in changeset.
Refactor two classes into a spec package

The previous package structure caused a package cycle.

Part of gradle/gradle-native#191

    • -1
    • +1
    ./BuildScanConfigIntegrationTest.groovy
  1. … 10 more files in changeset.
Allow for gracefully completely disabling build scans (#3291)

This is driven by scan functionality currently not working in the presence of source mappings. Previously, the scan plugin was reaching through internal and public incubating API, making it public API in effect, in order to work out if there were VCS mappings. Instead, we now use our existing insulation layer to convey this.

    • -13
    • +104
    ./BuildScanConfigIntegrationTest.groovy
  1. … 16 more files in changeset.
Expose auto applied `build-scan` plugin information

See gradle/kotlin-dsl#490

    • -3
    • +2
    ./BuildScanConfigIntegrationTest.groovy
  1. … 5 more files in changeset.
Automatically apply the build-scan plugin when `--scan` is provided on the command-line (#2832)

    • -0
    • +18
    ./BuildScanConfigIntegrationTest.groovy
  1. … 15 more files in changeset.
Calculate the build cache key when the build scan plugin has been applied (#2807)

    • -1
    • +21
    ./BuildScanConfigIntegrationTest.groovy
  1. … 13 more files in changeset.
Revert "Revert "Update build scan plugin to 1.8""

This reverts commit 0da2ef76e71ec9c24e5e875ad1a58e0e80f8a1ef.

    • -2
    • +2
    ./BuildScanConfigIntegrationTest.groovy
  1. … 3 more files in changeset.
Revert "Update build scan plugin to 1.8"

This reverts commit 3ee424e807952df581c778222c7d958b25bc85a2.

    • -2
    • +2
    ./BuildScanConfigIntegrationTest.groovy
  1. … 3 more files in changeset.
Update build scan plugin to 1.8

    • -2
    • +2
    ./BuildScanConfigIntegrationTest.groovy
  1. … 3 more files in changeset.
Update build scan plugin to 1.8

    • -2
    • +2
    ./BuildScanConfigIntegrationTest.groovy
  1. … 3 more files in changeset.
Bump the required build scan plugin version.

    • -1
    • +1
    ./BuildScanConfigIntegrationTest.groovy
  1. … 1 more file in changeset.
Only warn about missing build scan plugin once.

Previously, we would warn for each nested build.

    • -4
    • +29
    ./BuildScanConfigIntegrationTest.groovy
  1. … 6 more files in changeset.
Various fixes.

    • -4
    • +21
    ./BuildScanConfigIntegrationTest.groovy
  1. … 3 more files in changeset.
Rework the integration between the build scan plugin and Gradle so that we can gracefully fail if the plugin version isn't supported.

I also took the opportunity to make it more possible to evolve this integration going forward.

    • -0
    • +140
    ./BuildScanConfigIntegrationTest.groovy
  1. … 17 more files in changeset.