Gradle

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Adjust phrasing in composite builds user guide

+review REVIEW-6405

Adjust phrasing in composite builds user guide

+review REVIEW-6405

Merge pull request #993 from gradle/so-stable-perf-tests

Make TAPI performance tests fair

Make incubating messages more useful for build cache

Added more docs

Added more docs

Moved PluginId to an interface & docs

PluginId was pulled into an interface so that we can control the

creation of those instances.

Moved PluginId to an interface & docs

PluginId was pulled into an interface so that we can control the

creation of those instances.

Allow resolved artifacts as task input

A new type `ArtifactCollection` provides lazy access to the artifacts

resolved for a configuration, as a corollary to `FileCollection`.

This can be wired in as a task input, so that a task can use the

artifact metadata together with the resolved artifact files.

For now, `ArtifactCollection` is not handled natively as a task input,

but it provides a `FileCollection` property that can be declared as

the input for a task.

Still to come:

- Provide access to `ArtifactCollection` for a configuration view.

- Consistent builder API for access to `configuration.incoming.files`

and `configuration.incoming.artifacts`

- Handle `ArtifactCollection` natively as a task input

Make TAPI performance tests fair

The performance slightly depends on the length of the path to

the Gradle distribution. This change makes sure that all versions

under test use a path that is equally long.

Merge branch 'unhide-unstable-features'

This includes reverts for commits to 'hide stable features' on

the release branch. Doing it this way avoids conflicts on merge.

gradle/performance#252

Update `@Since 3.4`

gradle/performance#252

Revert "Hide unstable features from the release"

This reverts commit c9632e1ce8b443035bfdcae772fbba41b2461a8d.

gradle/performance#252

Revert "Hide more unstable methods from release"

This reverts commit 292f9d85af81d4bba04086764f6d9a7b3e776529.

gradle/performance#252

Hide more unstable methods from release

gradle/performance#252

Move memory health types from :core to :processServices

  1. … 26 more files in changeset.
Automatic convert Github issues to HTML link in the release note

Hide unstable features from the release

gradle/performance#252

TeamCity change in 'Gradle :: Branches :: Coverage Phase :: Linux Coverage' project: runners of 'Linux - Java 1.8 - Gradleception - Building Gradle with Gradle' build configuration were updated

TeamCity change in 'Gradle :: Branches :: Coverage Phase :: Linux Coverage' project: runners of 'Linux - Java 1.8 - Gradleception - Building Gradle with Gradle' build configuration were updated

Fix expected output in samples

Refine memory sampling event publishing

Move MemoryStatusBroadcaster startup to DefaultGradleLauncherFactory

Add support for ScheduledExecutors to ExecutorFactory

& Stoppable & honoring ExecutorPolicy

Move global scheduled executor creation to GlobalScopeServices

Don’t use anonymous broadcasters

DaemonHealthStats now consume memory sampling events

  1. … 6 more files in changeset.
Show action classloader hashes in build scan

+review REVIEW-6402

    • -3
    • +10
    /gradle/taskCacheBuildScanUserData.gradle
Adding tests for fork options on worker daemons

Move `configurationAttributesSchema` down to `DependencyHandler`

This commit fixes gradle/performance#251 by moving the attributes schema to the dependency handler. It's worth noting that

is also renames the configuration method from `configurationAttributesSchema` to simply `attributesSchema`.

  1. … 4 more files in changeset.
Tooling API: Support jdkName from idea module model

The information specified by

idea {

module {

jdkName = "My JDK"

}

}

is not made available by the tooling API. In order to fix

https://youtrack.jetbrains.com/issue/IDEA-138526

this change is required first. The language level is already handled automatically in recent versions of IDEA. However, if modules have different language levels, the project JDK is not suitable for them and you have to be able to set a module-specific JDK.

Find a better home for `Usage`

Fix Ivy publish integration test expectations

Fix expectations on Ivy samples integration tests

Use separate user home for each version under performance test

Until now, each performance test was using a separate test directory,

but the different versions under test were all using the same directory.

This meant that therer was a consistent bias depending on the order in which

the versions were executed.