Gradle

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Ensure that the implementation hash for a task defined in a Groovy DSL build script is the same when the task is deserialized from the instant execution cache as when it was serialized to cache.

Previously, a task defined in a Groovy DSL script was always treated as out-of-date when first deserialized from the instant execution cache.

Publish 6.0.1-20191120000030+0000

Do not hash the implementation classpath for a Groovy DSL script to use for in-memory script caching, but instead use the parent `ClassLoader` identity and the hash of the script itself, as this is faster and identifies the script implementation equally well.

This was the previous behavior, which was accidentally changed in a previous commit. This commit restores the previous behaviour but in a way that (hopefully) is harder to accidentally break in the future.

Rebaseline merge exclude rules

There seems to be small regression for some time now (2%/40ms).

This may be caused by memory pressure.

Rebaselining to unblock master.

Add incubating messages for VFS retention and partial invalida… (#11422)

Add incubating messages for VFS retention and partial invalidation

Merge branch 'master'

Move partial VFS invalidation test to own class

Do not use title case in incubation messages

Resolve injected changes to the root project's directory (#11410)

Resolve injected changes to the root project's directory

Get cache key length from hashing function used (#11405)

Get cache key length from hashing function used

Add incubating messages for VFS retention and partial invalidation

So it is easier to see if the system properties are picked up.

Enable partial vfs invalidation for the `gradle/gradle` build (#11409)

Enable partial vfs invalidation for the `gradle/gradle` build

Merge branch 'master'

Rebaseline GradleInceptionPerformanceTest

To accept a newly added API.

Disable the instant execution test suite again, as it seems to be quite flaky.

Attach `@ToBeFixedForInstantExecution` to several tests that appear to be flaky.

Remove http.keepAlive system property

Since https://github.com/gradle/dotcom/issues/1727 is done

Remove `@ToBeFixedForInstantExecution` annotations from some tests that now pass, and add to a couple that now don't pass.

Move dependency cache relocation out of promoted features

    • -10
    • +10
    /subprojects/docs/src/docs/release/notes.md
Recognize contributor

    • -0
    • +1
    /subprojects/docs/src/docs/release/notes.md
Merge branch 'patch-1' of https://github.com/bjornvester/gradle

* 'patch-1' of https://github.com/bjornvester/gradle:

Fix typo in command_line_interface.adoc

Publish 6.0.1-20191119000032+0000

Merge remote-tracking branch 'origin/release'

* origin/release:

Update to 6.0.1

Add note about 6.0 patch releases to release notes

Document GMM validation rules

Update to 6.0.1

    • -1
    • +1
    /gradle/wrapper/gradle-wrapper.properties
Publish 6.0.1

Skip test leaking test files with instant execution in :platformPlay

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

Rebaseline RealWorldNativePluginPerformanceTest

Use case-sensitive matching in the VFS caused another performance

regression of about 3% in `build on nativeMonolithic with 0 parallel workers`

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

Add comment to system property

Annotate tests failing with instant execution in CI-deferred :platformPlay

Follow up to https://github.com/gradle/gradle/pull/11309

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

Add note about 6.0 patch releases to release notes

    • -0
    • +2
    /subprojects/docs/src/docs/release/notes.md