Clone Tools
  • last updated a few seconds ago
Constraints: committers
Constraints: files
Constraints: dates
Merge pull request #12543 from gradle/eskatos/agp/upgrade

Update tested AGP versions

Skip AGP 4.1.0-alpha03 Santa Tracker caching smoke test

until next 4.1.0 release

because 4.1.0 nightly add some cached tasks

and update expected caching outcomes

Signed-off-by: Paul Merlin <>

Update ThirdPartyGradleModuleMetadataSmokeTest resources for AGP upgrade

Signed-off-by: Paul Merlin <>

Remove skipping of broken 4.1.0-alpha01 in smoke tests

Signed-off-by: Paul Merlin <>

Update under-test AGP versions

Signed-off-by: Paul Merlin <>

Publish 6.3-20200322000042+0000

Use normal task dependencies to model build types (#11788)

this fixes how build types are handled in the scanslist view

Add `@ToBeFixedForInstantExecution` to some new test cases.

Publish 6.3-20200321001401+0000

Merge pull request #12271 from gradle/bamboo/master/ie/cache-invalidation-after-buildSrc-changes

Invalidate instant execution cache upon changes to `buildSrc` task inputs

Merge pull request #12592 from gradle/wolfs/vfs/no-partial-invalidation-by-default

Do not enable partial invalidation in integTests

Polish `InstantExecutionCacheFingerprintWriter`

- Remove unnecessary `internal` modifiers

- Move non-essential method to the bottom

Polish `InstantExecutionFingerprintChecker`

- Rename parameter

- Re-order methods to shorten diff

Let `instantExecutionFingerprintWriter` be garbage collected

Merge pull request #12554 from gradle/bmuskalla/addBazelSupportInGenerator

add bazel support in generator

Recognize contributor

    • -0
    • +1
Merge pull request #12007 from jbaiera/add-executable-scala-compile

Pass executable setting to Scala Compiler

Add section title

Remove unused extension

Do not enable partial invalidation in integTests

we now run tests with watching enabled, that

should be enough to test partial invalidation

as well.

Add note about potential breaking changes

Merge pull request #12585 from gradle/wolfs/vfs/run-tests-automatically

Run VFS retention tests at least daily

Merge branch 'release'

Re-add verification metadata for old scan plugins

so init scripts don't fail.

Avoid unnecessary intersection computations

In the `gradle/gradle` build, all calls to _intersect_ were done

on the same sets of modules. Because we create immutable copies

every time, those were different instances.

By just checking, when we compute the _union_, that the sets are

the same, we avoid 100% of intersection calls in the `gradle/gradle`


Revert "Only run help for vfsRetentionTest"

We want to run the tests on `master`.

This reverts commit 50641cbb9b2d48057a0afd9b451c0bcf17f15c26.

Merge branch 'release'

Merge pull request #12589 from gradle/wolfs/vfs/only-help-for-vfs-retention-tests

Only run help for vfsRetentionTest

Only run help for vfsRetentionTest

So we don't run the tests on `release` when

we enable them on `master`.

Avoid eager creation of module identifier strings

and optimize `DefaultModuleIdentifier#toString`. This

showed up in a profiler snapshot in IDE sync: apparently this

code is invoked a lot. Because the calls to the loggers are not

guarded, the string representation is always created even if

logging is disabled.

The `toString()` method was using `String.format` which is

particularly slow.