Gradle

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Bump lib count in distribution test

Add :enterprise to the full distribution and use that for its tests

Create new configuration caching compatible enterprise plugin contact point (#13372)

  1. … 108 more files in changeset.
Merge pull request #13389 from gradle/bamboo/cc/review-ToBeFixed/i

Review tests annotated with `@ToBeFixedForInstantExecution`

Merge pull request #13391 from gradle/bamboo/cc/GenerateMavenPom/i

Make `GenerateMavenPom` compatible with the configuration cache

Merge pull request #13432 from gradle/wolfs/run-sub-trigger-without-dependencies

Add fs watching CI builds without dependencies

Add fs watching CI builds without dependencies

The experimental builds now don't depend on quick

feedback for faster feedback.

    • -6
    • +11
    /.teamcity/Gradle_Check/model/CIBuildModel.kt
Merge pull request #13335 from gradle/wolfs/vfs/watch-old-project-roots

Re-add JansiLibraryFactoryIntegrationTest (but move it to 'test' set)

This reverts commit f57762e38c533f64bb8c80049487c41e2b0b7bb6.

Use fully qualified task name for clarity

Unignore VFS retention tests

The tests should be fixed now

Merge branch 'master'

Rename handleWatcherChangeErrors -> withWatcherChangeErrorHandling

Move WatchRootUtil to watcher updater

Use hierarchies instead of roots to watch

Remove RootProjectDirectory

Ignore some tests under vfsRetentionTest (#13423)

Some tests are very fragile under vfsRetentionTest, ignore them

before we have a fix.

Merge pull request #13410 from gradle/jjohannes/gradle-build/gradle-distributions-plugin

Introduce GradleDistributionsPlugin for gradle/gradle build to model different distributions for integration testing

Rewrite @Unroll tests (#13425)

Change some of the artifact transform fixtures to use configuration cache friendly APIs to wire in producer tasks.

Use a convention to specify the default value for a project's build directory, so that build logic can also apply a convention to the build directory.

Restore the build directory for projects loaded from the configuration cache, so that artifact transforms applied to project dependencies use the correct workspace directory.

Do not eagerly execute artifact transforms for any file dependencies when writing to the configuration cache.

These files may change and so should be treated as configuration cache inputs if the result is eagerly cached. By lazily executing these transforms, these files do not need to be tracked as inputs to the configuration cache and the up-to-date checks for these transforms can happen in parallel during execution rather than at the start of the build.

Transforms for external remote dependencies are still run eagerly when writing the cache entry.

Ignore flaky InstantExecutionCacheCleanupIntegrationTest for now

Rebaseline JavaFirstUsePerformanceTest

It seems like we're creating more tasks which causes the scenarios

running slower.

Remove unused class.

Refine docs tests (#13406)

Merge pull request #13424 from gradle/am/cc/cache-diagnostics

Make the groovy DSL script cache lenient when an empty classes dir goes missing

Include all projects that are the target of a resolved project dependency in the configuration cache.

This allows the correct workspace to be calculated for an artifact transform of a file dependency, regardless of whether the file dependency is the output of a task or not. This in turn means that the transform will be up-to-date on the first read from the cache (assuming nothing else has changed).

  1. … 6 more files in changeset.
Use `ProjectStateRegistry` in a number of places that need to locate a project given its identity, rather than `ProjectFinder` which is intended to be used to resolve user provided paths relative to some project.

This avoids a bunch of unnecessary lookups during project dependency resolution and also fails when reading an artifact transform from the configuration cache when the corresponding project has not been serialized (for whatever reason) rather than silently treating the transform as a global transform.

  1. … 5 more files in changeset.