Clone Tools
  • last updated a few seconds ago
Constraints: committers
Constraints: files
Constraints: dates
Merge pull request #13519 from gradle/am/cc/transforms-II

Further fixes for artifact transforms with configuration cache enabled

Always instrument build logic, regardless of whether the configuration cache is enabled or not.

This change means that the same class paths and `ClassLoader` hierarchy are used regardless of whether or not the configuration cache is enabled. It also means that some cross-cutting instrumentation can later be added.

Reduce stale window size for PRs

We're still testing the bot to ensure it works properly.

Lowering the window size for PRs so some of the PRs are

actually affected.

Merge pull request #13495 from gradle/bamboo/cc/java/i

Don't rely on the artifact's existence to decide whether it should be published

Format `JavaPlatformPlugin`

Remove `@ToBeFixedForInstantExecution` from `SamplesMavenPublishIntegrationTest`

Format `MavenPublishResolvedVersionsJavaIntegTest`

Remove `@ToBeFixedForInstantExecution` from `SamplesCustomExternalTaskIntegrationTest`

Refine `@ToBeFixedForInstantExecution` of `SamplesCustomPluginIntegrationTest`

Remove `@ToBeFixedForInstantExecution` from `MavenPublishResolvedVersionsJavaIntegTest`

Remove `@ToBeFixedForInstantExecution` from `MavenPublishIdentifierValidationIntegTest`

Add test case for `Sync`

Closes #10960

Support more notations for `MavenPublication#artifact()`

Currently, there's no good way for a user to have a lazy artifact

provider, even if the producer is lazy (e.g, a `TaskProvider` or

a `Provider<RegularFile>`.

This commit fixes that by supporting more notations in the converter

and automatically using `LazyPublishArtifact` when a provider is


The lazy publish artifact now also supports more, in particular it

can accept any task as long as it provides a _single_ output file.

Fixes #7958

Make test in WarTaskIntegrationTest properly isolated

it was using a shared local build cache directory, making it sensible

to what tests were executed before, and fail when distributed

also, with the test being more strict it shown that something is wrong

when the configuration cache is enabled, added @ToBeFixed

Signed-off-by: Paul Merlin <>

Add some hand-crafted serialization for `PublishArtifactLocalArtifactMetadata` types to the configuration cache.

This is required because instances of this type use themselves as their own id, and so when serialized as an id (which is all that is required) drag in a lot of unnecessary and unserializable state.

A better change would be to separate out an immutable id from `PublishArtifactLocalArtifactMetadataCodec`, however the Eclipse tooling model builder currently takes advantage of the coupling to navigate from the id to the producing task for the artifact. Fixing this is too large a change for now and something that can happen later.

Publish 6.5-20200617230034+0000

Polish `DistributionPluginIntegrationTest`

Make `because` description more specific.

Remove `@ToBeFixedForInstantExecution` from `JavaCompileOnlyDependencyIntegrationTest`

Remove unnecessary mock setup from `DefaultMavenPublicationTest`

Remove unused import

Don't rely on the artifact's existence to decide whether it should be published

For compatibility with the configuration cache, the publication specs are

computed and filtered before the execution of tasks thus before artifacts have

been produced.

Merge pull request #13397 from gradle/bamboo/cc/PublishToMavenRepository/i

Make `PublishToMavenRepository` compatible with the configuration cache

Make `publishLocalPublicationToLocalRepository` compatible with the configuration cache

By moving the project extension access outside the task blocks.

Let configuration cache smoke test run `publishLocalPublicationToLocalRepository`

Fix Java attribute describer when category is missing

It's possible, during variant matching, that we match on the

category attribute with value "documentation", but that we

fail on the "docsType" attribute. In this case, when displaying

what didn't match, we want to make sure we can display a

reasonable error message. Currently because the "category" matched,

we just ignore the "docsType".

Merge pull request #13430 from gradle/vv/update-name-matcher-test-for-jdk15

Update NameMatcher test condition to pass with JDK15

Ignore conf cache reporting test on no-daemon executer

because post-build output behave differently

Signed-off-by: Paul Merlin <>

Disallow serializing `TaskDependency` instances to the configuration cache.

Ignore flaky tests

Make JavaApplicationDeploymentIntegrationTest not timeout