internal

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Rename FileMetadata{Snapshot -> }

Snapshot doesn't add anything to the name.

    • -1
    • +1
    ./controller/impl/DefaultBuildCacheCommandFactory.java
  1. … 50 more files in changeset.
Introduce access type on FileSystemLocationSnapshot

but don't fill it, yet.

    • -1
    • +2
    ./controller/impl/DefaultBuildCacheCommandFactory.java
  1. … 23 more files in changeset.
Introduce access type on FileSystemLocationSnapshot

but don't fill it, yet.

    • -1
    • +2
    ./controller/impl/DefaultBuildCacheCommandFactory.java
  1. … 23 more files in changeset.
Introduce access type on FileSystemLocationSnapshot

but don't fill it, yet.

    • -1
    • +2
    ./controller/impl/DefaultBuildCacheCommandFactory.java
  1. … 23 more files in changeset.
Extract file system operations around output creation

    • -0
    • +69
    ./packaging/impl/DefaultTarPackerFileSystemSupport.java
  1. … 6 more files in changeset.
Don't use `Task output caching` when talking about the build cache

The message whether the build cache is available mentions

task output caching, though that is never enabled. Only

the build cache can be enabled by e.g. `--build-cache`.

#11866

    • -1
    • +1
    ./services/BuildCacheControllerFactory.java
  1. … 1 more file in changeset.
Remove dependency between build-cache-packaging and native (#11856)

Part of: https://github.com/gradle/gradle-private/issues/2417

  1. … 7 more files in changeset.
Remove dependency between build-cache-packaging and native

Part of: https://github.com/gradle/gradle-private/issues/2417

  1. … 7 more files in changeset.
Remove dependency between build-cache-packaging and native

Part of: https://github.com/gradle/gradle-private/issues/2417

  1. … 7 more files in changeset.
Remove dependency between build-cache-packaging and native

Part of: https://github.com/gradle/gradle-private/issues/2417

  1. … 7 more files in changeset.
Merge the two BuildCacheServices classes

There is no point in keeping them separate.

    • -145
    • +0
    ./services/BuildCacheServices.java
  1. … 1 more file in changeset.
Move BuildCacheCommandFactory to :build-cache

And its implementation to :core (though it should end up in some build-cache-related subproject eventually).

    • -0
    • +179
    ./controller/impl/DefaultBuildCacheCommandFactory.java
  1. … 15 more files in changeset.
Fix checkstyle violations

  1. … 1 more file in changeset.
Extract interface from BuildCacheCommandFactory

  1. … 5 more files in changeset.
Remove dependency to native

By replacing the usage of FileSystem with a little utility class we can

get rid of the dependency between build-cache-packaging and native. For

this to work the TarBuildCacheEntryPackerPermissionTest hat to be

changes to assert correct permissions instead of checking for

interactions.

  1. … 7 more files in changeset.
Introduce a checksum file cache service

This service is responsible for caching the checksums computed from

local file system. Because it's also used for dependency verification

writing and checking, this cache uses the existing infrastructure which

makes sure that if a file is updated locally, we expire the entry in

the cache.

This is done because there are lots of places in the code where we

used the legacy `HashUtil` class, which has no caching whatsoever.

It's, however, quite common to have a build which generates sha1

checksums multiple times for the same file. For example, during

publication.

  1. … 102 more files in changeset.
Introduce a checksum file cache service

This service is responsible for caching the checksums computed from

local file system. Because it's also used for dependency verification

writing and checking, this cache uses the existing infrastructure which

makes sure that if a file is updated locally, we expire the entry in

the cache.

This is done because there are lots of places in the code where we

used the legacy `HashUtil` class, which has no caching whatsoever.

It's, however, quite common to have a build which generates sha1

checksums multiple times for the same file. For example, during

publication.

  1. … 102 more files in changeset.
Introduce a checksum file cache service

This service is responsible for caching the checksums computed from

local file system. Because it's also used for dependency verification

writing and checking, this cache uses the existing infrastructure which

makes sure that if a file is updated locally, we expire the entry in

the cache.

This is done because there are lots of places in the code where we

used the legacy `HashUtil` class, which has no caching whatsoever.

It's, however, quite common to have a build which generates sha1

checksums multiple times for the same file. For example, during

publication.

  1. … 102 more files in changeset.
Introduce a checksum file cache service

This service is responsible for caching the checksums computed from

local file system. Because it's also used for dependency verification

writing and checking, this cache uses the existing infrastructure which

makes sure that if a file is updated locally, we expire the entry in

the cache.

This is done because there are lots of places in the code where we

used the legacy `HashUtil` class, which has no caching whatsoever.

It's, however, quite common to have a build which generates sha1

checksums multiple times for the same file. For example, during

publication.

  1. … 103 more files in changeset.
Use native-platform to determine the hostname of the current machine.

Split a separate service out of `InetAddressFactory` to do the hostname resolution.

  1. … 5 more files in changeset.
Use native-platform to determine the hostname of the current machine.

Split a separate service out of `InetAddressFactory` to do the hostname resolution.

  1. … 7 more files in changeset.
Use native-platform to determine the hostname of the current machine.

Split a separate service out of `InetAddressFactory` to do the hostname resolution.

  1. … 7 more files in changeset.
Use native-platform to determine the hostname of the current machine.

Split a separate service out of `InetAddressFactory` to do the hostname resolution.

  1. … 7 more files in changeset.
Use native-platform to determine the hostname of the current machine.

Split a separate service out of `InetAddressFactory` to do the hostname resolution.

  1. … 7 more files in changeset.
Use native-platform to determine the hostname of the current machine.

Split a separate service out of `InetAddressFactory` to do the hostname resolution.

  1. … 6 more files in changeset.
Merge branch 'release'

Merge remote-tracking branch 'origin/master-test' into release-test

Inject hostname to OriginMetadataFactory

  1. … 4 more files in changeset.
Inject hostname to OriginMetadataFactory

  1. … 4 more files in changeset.
Move InetAddressFactory to :base-services and work around JDK bug

See https://bugs.openjdk.java.net/browse/JDK-8143378

  1. … 26 more files in changeset.