Clone Tools
  • last updated a few seconds ago
Constraints: committers
Constraints: files
Constraints: dates
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.


Update `@Since 3.4`


Revert "Hide unstable features from the release"

This reverts commit c9632e1ce8b443035bfdcae772fbba41b2461a8d.


Revert "Hide more unstable methods from release"

This reverts commit 292f9d85af81d4bba04086764f6d9a7b3e776529.


Hide more unstable methods from release


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


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
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

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.

Merge pull request #981 from gradle/so-fix-eclipse-file-dependencies

Fix local file dependency leak in IDE model

Merge branch 'release'

Check for password too

+review REVIEW-6404

ignore code quality samples test for java 9 to unblock ci chain

Fix performance regression in test execution

Regression was caused by removing support for class hierarchies in SerializerRegistry as worker protocol

for test execution relies on class hierarchies due to using interfaces and plain Object.class types.

Having multiple SerializerRegistry instances registered that support full class hierarchies causes trouble with

protocols using Object.class.

This was removed due to worker processes hanging when introducing new worker logging infrastructure.

- fix serialisation of test events to use custom serializer again instead of java serialisation

- fixed by explicitly setting class matching strategy in DefaultSerializerRegistry.

- remove Serializable interface from test event classes to avoid this kind of regression in the future

Task is not cacheable as it doesn't declare outputs

Move logic into parent class

Reuse logic

More test coverage for worker daemon failure scenarios

- Check failures when instantiating the runnable fails

- Check failures when the wrong parameters are passed to the worker daemon

Fix indentation