Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Handle rerun performance test

  1. … 7 more files in changeset.
Handle rerun performance test

  1. … 8 more files in changeset.
Handle rerun performance test

  1. … 8 more files in changeset.
Handle rerun performance test

  1. … 8 more files in changeset.
Handle rerun performance test

  1. … 7 more files in changeset.
Handle rerun performance test

  1. … 7 more files in changeset.
Handle rerun performance test

  1. … 8 more files in changeset.
Test rerun

  1. … 3 more files in changeset.
Test rerun

  1. … 2 more files in changeset.
Test rerun

  1. … 3 more files in changeset.
Revert "Revert "Take advantage of type-safe accessors in precompiled script plugins""

This reverts commit cbe1b9ed3f28e6fb39feaba56e8140f490dc5a6b.

  1. … 4 more files in changeset.
Revert "Take advantage of type-safe accessors in precompiled script plugins"

  1. … 4 more files in changeset.
Polish `api-parameter-names-index.gradle.kts`

Polish `api-parameter-names-index.gradle.kts`

Set tmpdir for test workers

  1. … 1 more file in changeset.
Remove unnecessary backticks

Update tagging plugin to 0.56

  1. … 1 more file in changeset.
Update tagging plugin to 0.56

  1. … 1 more file in changeset.
Update tagging plugin to 0.57

  1. … 1 more file in changeset.
Update tagging plugin to 0.56

  1. … 1 more file in changeset.
Improve tagging process

Update tagging plugin and fix incorrect parameter.

  1. … 3 more files in changeset.
Improve tagging process

Update tagging plugin and fix incorrect parameter.

  1. … 3 more files in changeset.
Update tag plugin

  1. … 1 more file in changeset.
Add an opt-out to automatic target jvm setting

Builds like Gradle have "incorrect" module setups: some modules

built for Java 6 have dependencies on Java 8 modules. This, in

general, shouldn't be allowed. However in Gradle it's "fine"

because we know that when we run on Java 6, the classes which

actually need Java 8 features or dependencies are not in use.

  1. … 6 more files in changeset.
Refine GRADLE_RERUNNER (#8522)

This is the followup of https://github.com/gradle/gradle/pull/8470 : there're two issues unresolved:

- `GRADLE_RERUNNER` is configured to `Gradleception`/`compileAll`/`sanityCheck`, etc. , which makes no sense.

- We want to skip `GRADLE_RERUNNER` if there're too many failures.

This PR does:

- Extract another function `applyTestDefaults` in addition to `applyDefaults`. Functional test build and smoke test build apply `applyTestDefaults`.

- Slightly refactor `applyDefaults` function.

- Add unit tests for `applyTestDefaults`/`applyDefaults`.

- Switch to JUnit 5 for `.teamcity` project.

- Ignore the rerun if test failures are > 10.

  1. … 6 more files in changeset.
Fix cache-hit in flakiness detection performance test (#8482)

We don't want build cache hit in performance flakiness detection, however, previously the coordinator build resolves "flakiness-detection-commit" baseline to real commit id "5.3-commit-237a600", resulting in unexpected cache hit.

This PR fixes it by:

- On coordinator's side, pass "flakiness-detection-commit" as it is to worker build.

- On worker's side, worker build resolves "flakiness-detection-commit" to real commit version - this disables build cache.

Since `DetermineBaselines` is becoming more and more complex, this PR also adds a unit test for `DetermineBaselines` class.

  1. … 3 more files in changeset.
Add a build step which reruns previous failed test classes (#8470)

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

We've been bitten by flaky tests for a long time. This PR adds an extra build step which reruns failed test classes again.

  1. … 3 more files in changeset.
Use 'repo.gradle.org' as repository URL

  1. … 1 more file in changeset.
Detect flaky performance test scenarios (#8367)

As part of https://github.com/gradle/gradle-private/issues/1635 , we want to detect flaky performance test with a weekly job, in order to know which scenarios are flaky.

  1. … 21 more files in changeset.
Replace :patchExternalModules with :kotlinCompilerEmbeddable

Only the kotlin-compiler-embeddable jar needs to be patched now.

Some patch actions were not needed anymore.

There's now a :kotlinCompilerEmbeddable subproject responsible for

building the patched kotlin-compiler-embeddable jar.

Only :kotlinDsl depends on it.

This greatly simplified the setup in the root project build script.

Various places required to be adjusted to account for the new setup.

The patching itself was rewritten to work in a streaming fashiong to

reduce i/o operations and disk usage. It was also moved up the

dependency tree.

All in all this should provide with a noticeable build speed up.

Signed-off-by: Paul Merlin <paul@gradle.com>

    • -100
    • +0
    ./kotlin/org/gradle/modules/JarPatcher.kt
  1. … 8 more files in changeset.