Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Automate bucket generation

  1. … 16 more files in changeset.
Automate bucket generation

  1. … 16 more files in changeset.
Automatically determine if `origin` should be used (#11580)

This commit changes how the `DetermineBaselines` task figures out

where to fetch sources. It was assuming a remote named `origin`,

but in practice it can be anything else, in particular `upstream`.

Now we will ask Git for the remotes and find the upstream one.

Update buildSrc/subprojects/plugins/src/main/kotlin/org/gradle/plugins/performance/DetermineBaselines.kt

Automatically determine if `origin` should be used

This commit changes how the `DetermineBaselines` task figures out

where to fetch sources. It was assuming a remote named `origin`,

but in practice it can be anything else, in particular `upstream`.

Now we will ask Git for the remotes and find the upstream one.

Combine and rewrite all documentation generation

    • -22
    • +0
    ./kotlin/gradlebuild/jsoup.gradle.kts
  1. … 274 more files in changeset.
Automate bucket generation

  1. … 13 more files in changeset.
Annotate command-line arg provider names with Internal

to remove the deprecation warnings.

  1. … 1 more file in changeset.
Test new baseline

  1. … 1 more file in changeset.
Add OS as inputs for unit tests (#11310)

This closes https://github.com/gradle/gradle-private/issues/2831

Previously we only add OS as inputs for integration tests but not for unit tests. This results in missing test coverage for some unit tests.

We need to add OS as inputs of unit test task as well.

  1. … 1 more file in changeset.
Remove OS inputs from DistributionTest

  1. … 1 more file in changeset.
Add OS as inputs for unit tests

Add OS as inputs for unit tests

Push the logic that figures out the tools classpath for the test JVM down from the build script and into the model object.

  1. … 2 more files in changeset.
Push the logic that figures out the tools classpath for the test JVM down from the build script and into the model object.

  1. … 2 more files in changeset.
Some polishing of the build logic to locate the various JVMs used by the build.

- Apply the `AvailableJavaInstallationsPlugin` to all projects, rather than the root project.

- Add some modelling to the extension added by the plugin.

- Make sure the plugins that expect the extension to be present to explicitly state this (by applying the plugin).

  1. … 6 more files in changeset.
Some polishing of the build logic to locate the various JVMs used by the build.

- Apply the `AvailableJavaInstallationsPlugin` to all projects, rather than the root project.

- Add some modelling to the extension added by the plugin.

- Make sure the plugins that expect the extension to be present to explicitly state this (by applying the plugin).

  1. … 6 more files in changeset.
Some polishing of the build logic to locate the various JVMs used by the build.

- Apply the `AvailableJavaInstallationsPlugin` to all projects, rather than the root project.

- Add some modelling to the extension added by the plugin.

- Make sure the plugins that expect the extension to be present to explicitly state this (by applying the plugin).

  1. … 6 more files in changeset.
Rework the discovery and validation of the JVMs used for building, compiling and testing Gradle, so that the implementation is compatible with instant execution.

In particular, model the `AvailableJavaInstallations` as a 'build service', in part to dogfood this API. Also remove some logic that is no longer required.

  1. … 5 more files in changeset.
Rework the discovery and validation of the JVMs used for building, compiling and testing Gradle, so that the implementation is compatible with instant execution.

In particular, model the `AvailableJavaInstallations` as a 'build service', in part to dogfood this API. Also remove some logic that is no longer required.

  1. … 5 more files in changeset.
Rework the discovery and validation of the JVMs used for building, compiling and testing Gradle, so that the implementation is compatible with instant execution.

In particular, model the `AvailableJavaInstallations` as a 'build service', in part to dogfood this API. Also remove some logic that is no longer required.

  1. … 5 more files in changeset.
Follow local platform dependencies for runtime classpath in manifest

Follow local platform dependencies for runtime classpath in manifest

Follow local platform dependencies for runtime classpath in manifest

Don't try to build commit distribution on Windows

Don't try to build commit distribution on Windows

Don't try to build commit distribution on Windows

Use gradlew.bat on Windows

Use gradlew.bat on Windows

Use gradlew.bat on Windows