Gradle

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Publish 5.6-20190801230839+0000

Change instant execution serialization to write the edges between work nodes to the cache, instead of the dependencies between tasks.

This will allow nodes other than tasks to be deserialized and added back to the work graph. Also short-circuit the node dependency calculation when reading nodes back from the cache, as the calculation has already been done.

Change instant execution to serialize all work nodes to the cache, rather than just the task nodes.

In this change, only a placeholder is written to the cache for node that are not task nodes, and this are discarded on read.

Merge pull request #10148 from gradle/lptr/transforms/fail-build-on-invocation-creation-error

Fail build if invocation creation fails

Fail build if invocation creation fails

If that happens we have some problem with Gradle logic.

Temporarily ignore instant execution performance tests

While investigating the regression on a separate branch.

Merge pull request #10115 from gradle/lptr/build-caxhe/no-cleanup-after-unpack-failure

Fail on unpack failure

Merge pull request #10118 from gradle/lptr/execution/optional-execution-store

Remove UnitOfWork.isTaskHistoryMaintained()

Write a placeholder to the instant execution cache for each artifact transform output included in a file collection and that is scheduled for execution. The placeholder is ignored on read from the cache, so the outputs of artifact transforms are still being discarded.

Publish 5.6-20190731230038+0000

Merge pull request #10126 from gradle/revert-10125-revert-9940-eskatos/ie/spike-reuse-classloaders

Reinstate "Let instant execution reuse classloaders when loading"

Improve rendering of artifacts in outgoing variants report

This commit changes how artifacts are rendered, so that if they

are associated with a type (either explicit or derived), we show

the corresponding `artifactType` attribute.

This helps understanding a bit what can happen in an Android build

where multiple variants may have the same attributes, but only

differ on the artifact type derived from the artifacts carried

by the variant.

Adjust regex to fix flaky test (#10116)

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

Merge pull request #10123 from gradle/wolfs/flaky/fix-security-manager-integ-test

Fix flaky SecurityManagerIntegrationTest

Revert "Revert "Let instant execution reuse classloaders when loading""

  1. … 22 more files in changeset.
Merge pull request #10125 from gradle/revert-9940-eskatos/ie/spike-reuse-classloaders

Revert "Let instant execution reuse classloaders when loading"

Revert "Let instant execution reuse classloaders when loading"

  1. … 22 more files in changeset.
Merge pull request #9940 from gradle/eskatos/ie/spike-reuse-classloaders

Let instant execution reuse classloaders when loading

Publish 5.6-20190730230302+0000

Polish `InstantExecutionClassLoaderScopeRegistryListener`

Polish `DefaultInstantExecution`

- Reduce overhead of `ClassLoaderSpec` collections

Document `ClassLoaderScopeRegistryListener`

Publish 5.6-20190730213615+0000

Fix flaky SecurityManagerIntegrationTest

The test executor is often number 3.

Fixes gradle/gradle-private#2254

Fix test for Windows

Merge pull request #10120 from gradle/wolfs/teamcity/fewer-forks-on-macos

Use fewer parallel forks on macOS

Make codenarc happy

Simplify map chain

Use fewer parallel forks on macOS

since the agents are not very powerful.

Fix test expectation