BuildScanAutoApplyIntegrationTest.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>

    • -12
    • +12
    ./BuildScanAutoApplyIntegrationTest.groovy
  1. … 872 more files in changeset.
Annotate integ tests failing with instant execution in various projects

after first round of CI feedback

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

    • -0
    • +2
    ./BuildScanAutoApplyIntegrationTest.groovy
  1. … 58 more files in changeset.
Annotate integ tests failing with instant execution in various projects

after first round of CI feedback

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

    • -0
    • +2
    ./BuildScanAutoApplyIntegrationTest.groovy
  1. … 58 more files in changeset.
Annotate integ tests failing with instant execution in :core

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

    • -0
    • +10
    ./BuildScanAutoApplyIntegrationTest.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
    • +10
    ./BuildScanAutoApplyIntegrationTest.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
    • +11
    ./BuildScanAutoApplyIntegrationTest.groovy
  1. … 100 more files in changeset.
Fix handling of “no settings” case WRT auto applied plugins and classpath

Some invocation args (e.g. -b) cause us to create two settings objects,

with the subsequent being empty.

Previously we were applying the auto

apply plugins to both, and inheriting the empty's classpath into the

rest of the build.

Now, we don't auto apply any plugins to the empty and have it inherit

the real settings script's classpath (which also makes it available to

the rest of the build tree).

Closes #11101

    • -9
    • +17
    ./BuildScanAutoApplyIntegrationTest.groovy
  1. … 3 more files in changeset.
Integrate with Gradle Enterprise plugin 3.0 (#11041)

    • -105
    • +97
    ./BuildScanAutoApplyIntegrationTest.groovy
  1. … 52 more files in changeset.
Fail better when using --scan and an old incompatible scan plugin

    • -2
    • +22
    ./BuildScanAutoApplyIntegrationTest.groovy
  1. … 3 more files in changeset.
Update scan support for Gradle Enterprise plugin 3.0

Gradle 6 is now only compatible with this plugin.

    • -105
    • +77
    ./BuildScanAutoApplyIntegrationTest.groovy
  1. … 35 more files in changeset.
Revert "Disable auto apply for scan plugin (temporally) (#10783)"

This reverts commit 5b1d0543e4b76fc51aafb5d2fc757dcf086b0e4c.

    • -2
    • +0
    ./BuildScanAutoApplyIntegrationTest.groovy
  1. … 5 more files in changeset.
Disable auto apply for scan plugin (temporally) (#10783)

* Disable auto apply for scan plugin

This will be reenabled as soon as possible once we integrated that gradle snapshot into the ge

    • -0
    • +2
    ./BuildScanAutoApplyIntegrationTest.groovy
  1. … 5 more files in changeset.
Ignore auto apply related tests

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

    • -13
    • +12
    ./BuildScanAutoApplyIntegrationTest.groovy
  1. … 13 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.

    • -1
    • +1
    ./BuildScanAutoApplyIntegrationTest.groovy
  1. … 16 more files in changeset.
Add test case for applying the build scan plugin from a script plugin

Attempt an initial solution which doesn't work yet.

    • -2
    • +45
    ./BuildScanAutoApplyIntegrationTest.groovy
  1. … 8 more files in changeset.
Merge branch 'release'

    • -0
    • +18
    ./BuildScanAutoApplyIntegrationTest.groovy
  1. … 2 more files in changeset.
Fix built-in scans when buildscript block has apply statements

Built-in scans were breaking with a common pattern where a

script is applied inside the buildscript block, usually in order

to provide a list of commonly used versions for usage inside the block.

This is now fixed by only trying to apply plugin requests when the

script target supports the plugins block.

    • -0
    • +18
    ./BuildScanAutoApplyIntegrationTest.groovy
  1. … 2 more files in changeset.
Expose auto applied `build-scan` plugin information

See gradle/kotlin-dsl#490

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

    • -0
    • +253
    ./BuildScanAutoApplyIntegrationTest.groovy
  1. … 15 more files in changeset.