Gradle

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Add some test coverage for configuration cache support for artifact transforms.

Publish 6.5-20200622230111+0000

Merge pull request #13549 from gradle/wolfs/vfs/better-error-on-unsupported-os

Gracefully handle when file-events library can't be loaded

Initialize file event functions in constructor

Merge pull request #13545 from gradle/eskatos/cc/merge-report-files

Let the configuration cache report be a self contained file

Do not test lines after data is written

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

Move native services dir out of testkit home

for `UndeclaredBuildInputsTestKitInjectedJavaPluginIntegrationTest`.

See the same code in `BaseGradleRunnerIntegrationTest`.

This avoids left-over native platform library

files.

Gracefully handle when file-events library can't be loaded

We now try to load the native file-system

watching integration on daemon startup and

log the failure if it can't be loaded.

See #13396

Upgradle to latest nightly

So we don't watch the cache directories when

file-system watching is enabled.

    • -1
    • +1
    /gradle/wrapper/gradle-wrapper.properties
Write the artifact transforms for external dependencies to the configuration cache as a spec, rather than eagerly running the transform and writing the resulting files to the cache.

This means that no transforms are run eagerly. All transforms may take task outputs or other changing files as parameters and it is not easy to determine whether or not this is the case. So, for now assume that all transforms have changing parameters. A later improvement could be to eagerly run transforms for remote artifacts that do not have changing parameters.

  1. … 9 more files in changeset.
Fix JavaProcessStackTracesMonitor hanging

Previously we observed some JavaProcessStackTracesMonitor hanging issues.

It was because we didn't call `process.waitFor()` properly.

Catch Throwable when parsing performance test results

Previously we use `catch(e)` which only catches `Exception`, when

there's `Error` thrown, it fails the build.

Ignore hanging test for now

Publish 6.5-20200621230124+0000

Simplify extraction of configuration cache report data

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

Publish 6.5-20200620230302+0000

Update cc doc on reporting issue now that the report is a single file

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

Code quality test the configuration cache report code

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

Add test to prevent breaking the report dev workflow

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

Merge pull request #13533 from gradle/bamboo/cc/java/iii

Capture `Jar` manifest generator in the configuration cache

Let the report be a self contained file

by inserting the data in the generated html file

making it very easy to share

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

Merge configuration cache report assets into a single file

The number of files raised with the new style.

Generated report is now just a .html file and the -data.js file.

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

Merge pull request #13525 from gradle/eskatos/agp/update

Update tested AGP versions

Merge pull request #13517 from gradle/eskatos/cc/report-design

Style the configuration cache problems report

Remove python from code analysis

    • -1
    • +1
    /.github/workflows/codeql-analysis.yml
Explicitly declare CodeQL analysis languages

    • -3
    • +2
    /.github/workflows/codeql-analysis.yml
Publish 6.5-20200619233717+0000

Run CodeQL analysis with JDK 11

    • -0
    • +6
    /.github/workflows/codeql-analysis.yml
Fix CI in GitHub Action

Fix wrapping on report with deeply nested graphs

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