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

Combine and rewrite all documentation generation

    • -22
    • +0
    ./kotlin/gradlebuild/jsoup.gradle.kts
  1. … 274 more files in changeset.
Annotate command-line arg provider names with Internal

to remove the deprecation warnings.

  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.
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.
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.
Pin all remote projects to exact refs, don't use branches

Pinning to branches means the build is not fully reproducible, as changes in the remote repo can alter the outcome of this build.

  1. … 3 more files in changeset.
Use dedicated user with token-based authentication to execute… (#11044)

Replace password-based authentication with token in distributed performance tests

  1. … 7 more files in changeset.
Use dedicated user with token-based authentication to execute… (#11044)

Replace password-based authentication with token in distributed performance tests

  1. … 7 more files in changeset.
Use dedicated user with token-based authentication to execute… (#11044)

Replace password-based authentication with token in distributed performance tests

  1. … 7 more files in changeset.
Use branch instead of tag for green branch

Use branch instead of tag for green branch

Force update green branch tags

Force update green branch tags

Set a green branch tag when Ready for nightly finishes (#10984)

Fixes https://github.com/gradle/gradle-private/issues/1398

This PR sets up a "green status" for master/release branch,

which can be used by user to checkout new branches.

    • -0
    • +44
    ./kotlin/org/gradle/gradlebuild/UpdateBranchStatus.kt
  1. … 3 more files in changeset.
Set a green branch tag when Ready for nightly finishes (#10984)

Fixes https://github.com/gradle/gradle-private/issues/1398

This PR sets up a "green status" for master/release branch,

which can be used by user to checkout new branches.

    • -0
    • +44
    ./kotlin/org/gradle/gradlebuild/UpdateBranchStatus.kt
  1. … 3 more files in changeset.
Fix empty REPO_MIRROR_URLS

Remove `distributedFullPerformanceTest(s)`

  1. … 1 more file in changeset.
Add new experiment coordinator build

which runs once a week. The historical coordinator now only runs

regression tests.

  1. … 2 more files in changeset.
Run only slow regression tests every day

and maybe later on every commit on `master`. The experiments are

already run weekly as part of the `historical` performance tests.

  1. … 2 more files in changeset.
Make buckets in TeamCity configuration (#10552)

Currently, the primary obstacles for us to improve CI feedback time is the long-running jobs: `integTest`/`core`/`dependencyManagement` each takes more than 10 minutes. Without decreasing the time we can't improve CI feedback time.

This PR changes the previous subproject-based TC job to bucket-based TC job: a bucket can contain a split of large subproject, or many tiny subprojects. This makes CI configuration more flexiable and efficient.

For example, all tiny subprojects which only contain unit tests can be merged to `AllUnitTests`, just as before - but now we make this more generic.

`integTest` subproject can be split to 3 jobs: `integTest`/`integTest_2`/`integTest_3`. Splitted project has a special parameter `-PtestSplit=1/3`/`-PtestSplit=2/3`/`-PtestSplit=3/3` so the build can choose only a subset of tests to execute.

  1. … 8 more files in changeset.
Make buckets in TeamCity configuration (#10552)

Currently, the primary obstacles for us to improve CI feedback time is the long-running jobs: `integTest`/`core`/`dependencyManagement` each takes more than 10 minutes. Without decreasing the time we can't improve CI feedback time.

This PR changes the previous subproject-based TC job to bucket-based TC job: a bucket can contain a split of large subproject, or many tiny subprojects. This makes CI configuration more flexiable and efficient.

For example, all tiny subprojects which only contain unit tests can be merged to `AllUnitTests`, just as before - but now we make this more generic.

`integTest` subproject can be split to 3 jobs: `integTest`/`integTest_2`/`integTest_3`. Splitted project has a special parameter `-PtestSplit=1/3`/`-PtestSplit=2/3`/`-PtestSplit=3/3` so the build can choose only a subset of tests to execute.

  1. … 8 more files in changeset.
Move rerun strategy to property

and add some DSL to configure it.

  1. … 4 more files in changeset.
Remove unused code

  1. … 2 more files in changeset.
New performance process (#10361)

This PR introduces new performance test process. See more details in https://docs.google.com/document/u/1/d/1pghuxbCR5oYWhUrIK2e4bmABQt3NEIYOOIK4iHyjWyQ/edit#heading=h.is4fzcbmxxld

  1. … 50 more files in changeset.
Prefer composition over inheritance in PerformanceTest hierarchy (#10262)

### Context

Previously, we had a bad `PerformanceTest` hierarchy:

- PerformanceTest

- ReportGenerationPerformanceTest

- BuildScanPerformanceTest

- DistributedPerformanceTest

- RerunDistributedPerformanceTest

This PR does a refactoring - extracts a `PerformanceTestReporter`/`DistributedPerformanceTestReporter` out of the `PerformanceTest` hierarchy, because https://github.com/gradle/gradle-private/issues/2192 wants a report, too.

The hierarchy after the refactoring:

- PerformanceTest

- DistributedPerformanceTest

- PerformanceTestReporter

So we can make things easier.

  1. … 10 more files in changeset.
Allow running build types for multiple subprojects at once

So we can invoke e.g. `baseServices:quickTest cli:quickTest`.

Allow running build types for multiple subprojects at once

So we can invoke e.g. `baseServices:quickTest cli:quickTest`.

Add missing type information to `PerformanceTestPlugin`

For compatibility with Kotlin 1.3.41.