Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Fix build scan performance test to use new enterprise plugin

Use daemon by default in cross build tests

  1. … 6 more files in changeset.
Rename CrossBuild{ -> GradleInternal}PerformanceTestRunner

  1. … 5 more files in changeset.
First working versino

  1. … 11 more files in changeset.
Explicitly pass env variables for build scan performance tests

- enable preemptive authentication

  1. … 1 more file in changeset.
Add authentication for resolving scan plugin snapshots

Update performance tests template to not use deprecated configurations

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.
Refactor old ReportGenerator

  1. … 43 more files in changeset.
Refactor old ReportGenerator

  1. … 44 more files in changeset.
Rename performance test infrastructure legacy classes

To make clear that they are using the Gradle build internal

infrastructure.

  1. … 43 more files in changeset.
Remove start and end from MeasuredOperation

The fields are unused and we can't fill them from Gradle profiler.

  1. … 4 more files in changeset.
Remove start and end from MeasuredOperation

The fields are unused and we can't fill them from Gradle profiler.

  1. … 4 more files in changeset.
Allow using Gradle profiler in cross version tests

  1. … 12 more files in changeset.
Allow using Gradle profiler in cross version tests

  1. … 11 more files in changeset.
Allow using Gradle profiler in cross version tests

  1. … 12 more files in changeset.
Allow using Gradle profiler in cross version tests

  1. … 12 more files in changeset.
Upgrade Groovy version to customized 1.1-2.5.7

  1. … 39 more files in changeset.
Upgrade Groovy version to customized 1.1-2.5.7

  1. … 40 more files in changeset.
Upgrade Groovy version to customized 1.1-2.5.7

  1. … 39 more files in changeset.
Upgrade Groovy version to customized 1.1-2.5.7

  1. … 40 more files in changeset.
Upgrade Groovy version to customized 1.0-2.5.7

x

  1. … 39 more files in changeset.
Unify Groovy versions to 2.5.4

  1. … 35 more files in changeset.
Unify Groovy versions to 2.5.4

  1. … 35 more files in changeset.
Unify Groovy versions to 2.5.4

  1. … 35 more files in changeset.
Unify Groovy versions to 2.5.4

  1. … 35 more files in changeset.
Upgrade Groovy to 2.5.7

  1. … 39 more files in changeset.
Unify Groovy versions to 2.5.4

  1. … 35 more files in changeset.
Mark known flaky performance test in report (#8997)

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

We want to mark the known performance test scenarios in the report even when they pass. This can give us insights of how the scenarios work previously. In this way, we can easily know, "this scenario fails, ah, it's marked as flaky", or, "this scenario is improved, but hold on, it's marked as flaky, let's not rebaseline it".

  1. … 13 more files in changeset.
Do not use singleton patter for FlakinessAnalyzer

A field is just as good.

  1. … 6 more files in changeset.