Gradle

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Change `Provider.map()` and `Provider.flatMap()` to allow `null` to be returned by the mapping function.

Change `Provider.map()` and `Provider.flatMap()` to allow `null` to be returned by the mapping function.

Change `Provider.map()` and `Provider.flatMap()` to allow `null` to be returned by the mapping function.

Change `Provider.map()` and `Provider.flatMap()` to allow `null` to be returned by the mapping function.

Remove no longer applicable `@ToBeFixedForInstantExecution`

Remove `@ToBeFixedForInstantExecution` annotation from fixed tests

Preserve cache key format when there are no excluded task names

Polish `DefaultInstantExecution`

Mark tests that rely on build listeners `@ToBeFixedForInstantExecution`

Add excluded task names to the instant execution cache key

Add relative invocation dir to the instant execution cache key as needed

Because relative task names are resolved relative to the enclosing subproject

according to the invocation dir (`StartParameter.currentDir`).

Allow multiple distinct user input using tooling API

WIP

WIP

Allow multiple distinct user input using tooling API

Reactivate reselection on selector removal

Fixes #6567

The remaining issue reported in #11789 is fixed by the previous commit.

Fix re-selection cycle with endorsing parent nodes

Fixes issue reported in this comment:

https://github.com/gradle/gradle/issues/11789#issuecomment-572777215

Add test to reproduce exception on re-selection

https://github.com/gradle/gradle/issues/11789#issuecomment-572777215

Add test case for read-only cache with containers

This commit introduces a test case to check that it's actually

possible to run concurrent docker containers using the same

shared, read-only, dependency cache. It acts both as a test

case and documentation, as mounting the cache as a read-only

volume in Docker is the recommended behavior.

  1. … 4 more files in changeset.
Add test case for read-only cache with containers

This commit introduces a test case to check that it's actually

possible to run concurrent docker containers using the same

shared, read-only, dependency cache. It acts both as a test

case and documentation, as mounting the cache as a read-only

volume in Docker is the recommended behavior.

  1. … 4 more files in changeset.
Add test case for read-only cache with containers

This commit introduces a test case to check that it's actually

possible to run concurrent docker containers using the same

shared, read-only, dependency cache. It acts both as a test

case and documentation, as mounting the cache as a read-only

volume in Docker is the recommended behavior.

  1. … 4 more files in changeset.
Add test case for read-only cache with containers

This commit introduces a test case to check that it's actually

possible to run concurrent docker containers using the same

shared, read-only, dependency cache. It acts both as a test

case and documentation, as mounting the cache as a read-only

volume in Docker is the recommended behavior.

  1. … 4 more files in changeset.
Add test case for read-only cache with containers

This commit introduces a test case to check that it's actually

possible to run concurrent docker containers using the same

shared, read-only, dependency cache. It acts both as a test

case and documentation, as mounting the cache as a read-only

volume in Docker is the recommended behavior.

  1. … 4 more files in changeset.
Add test case for read-only cache with containers

This commit introduces a test case to check that it's actually

possible to run concurrent docker containers using the same

shared, read-only, dependency cache. It acts both as a test

case and documentation, as mounting the cache as a read-only

volume in Docker is the recommended behavior.

  1. … 4 more files in changeset.
Add test case for read-only cache with containers

This commit introduces a test case to check that it's actually

possible to run concurrent docker containers using the same

shared, read-only, dependency cache. It acts both as a test

case and documentation, as mounting the cache as a read-only

volume in Docker is the recommended behavior.

  1. … 4 more files in changeset.
Add test case for read-only cache with containers

This commit introduces a test case to check that it's actually

possible to run concurrent docker containers using the same

shared, read-only, dependency cache. It acts both as a test

case and documentation, as mounting the cache as a read-only

volume in Docker is the recommended behavior.

  1. … 4 more files in changeset.
Polish `DefaultInstantExecution`

Let instant execution honor the build layout

Refine AndroidTestProject

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

Remove dead code in AndroidGradlePluginVersions fixture

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