Gradle

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
print on cme

Calculate exception lazily

Print stacktraces at entrance

Fix 404 in performance test coordinator (#10036)

### Context

This fixes https://github.com/gradle/gradle-private/issues/2273

Previously we got 404 when trying to fetch build status from TC. The exception

will break report generation. This commit fixes the issue by catching the 404

exception correctly.

Publish 5.6-20190723234933+0000

Remove no longer relevant TODOs

- `@Nullable` cannot be applied to type arguments

- Software model questions are no longer relevant

Merge pull request #9968 from gradle/bamboo/ie/migrate-to-new-Kotlin-js-plugin

Migrate to new Kotlin Js plugin

Merge pull request #10055 from gradle/bamboo/master/fix-instant-execution-report-jar

Fix `:instantExecutionReport` jar not to include duplicate entries

Fix `:instantExecutionReport` jar not to include duplicate entries

Merge branch 'release'

Merge pull request #9461 from gradle/wolfs/xforms/support-nested

Generate read-only user type properties

    • -0
    • +8
    /subprojects/docs/src/docs/release/notes.md
Address review feedback

Rebaseline all performance test scenarios

There seems to be tiny gradual regression in performance, which causes unbearable

flakiness. Rebaselining all scenarios to catch future regressions.

  1. … 16 more files in changeset.
Rebaseline NativeCleanBuildPerformanceTest

It seems to have gradual tiny regressions. Rebaselining.

Rebaseline TaskOutputCachingSwiftPerformanceTest

TaskOutputCachingSwiftPerformanceTest seems to have a small regression

since long time ago. Rebaselining it.

Change the instant execution cache bean serialization so that it honors the `writeReplace()` contract for `Serializable` types.

This allows a plugin to use the Guava collection types, which happen to use this contract for serialization. This could be viewed as a work around for the lack of support for multiple classes with the same name (and that is certainly the motivation). However, this provides a potential escape hatch for plugin authors to work around serialization issues. It also provides a nice migration path for re-using the bean serialization in other places, such as task properties, isolated work parameters and tooling models, all of which currently use Java Serialization as the general purpose contract.

Publish 5.6-20190722230056+0000

Add specific serialization to the instant execution cache for the Guava immutable collection types. These are the classes used by Gradle core, not those that a plugin may happen to use (which are still not supported).

Represent classes serialized to the instant execution cache using an integer id, rather than a string class name.

Apart from reducing the amount of stuff written to the cache, this will also allow multiple classes with the same name (but different ClassLoaders) to be referenced in the instant execution state.

Merge branch 'release'

Update internal_build_cache_issue

Update to latest nightly

    • -1
    • +1
    /gradle/wrapper/gradle-wrapper.properties
Rebaseline some scenarios

We saw gradual regression in some of the scenarios. Rebaseling them.

Rebaseline some scenarios

We saw gradual regression in some of the scenarios. Rebaseling them.

Rebaseline to latest nightly

Looking at the history, last rebaselining seems not to use the right version,

so this is rebaselining to latest nightly.

Rebaseline to latest nightly

Looking at the history, last rebaselining seems not to use the right version,

so this is rebaselining to latest nightly.

Fix typo (#10030)

Publish 5.6-20190720230102+0000

Avoid merging old mappings on full recompilation (#9964)

This fixes https://github.com/gradle/gradle/issues/9936

Previously even on full recompilation, we merge the old Groovy source-class mappings

into the incremental mappings. This PR avoid doing this on full recompilation.

Avoid merging old mappings on full recompilation (#9964)

This fixes https://github.com/gradle/gradle/issues/9936

Previously even on full recompilation, we merge the old Groovy source-class mappings

into the incremental mappings. This PR avoid doing this on full recompilation.