Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Remove unused build logic

  1. … 2 more files in changeset.
Remove unused build logic

  1. … 2 more files in changeset.
Simplify build type plugin

  1. … 5 more files in changeset.
Simplify build type plugin

  1. … 5 more files in changeset.
Simplify build type plugin

  1. … 5 more files in changeset.
Simplify build type plugin

  1. … 4 more files in changeset.
Simplify build type plugin

  1. … 5 more files in changeset.
Simplify build type plugin

  1. … 5 more files in changeset.
Simplify build type plugin

  1. … 5 more files in changeset.
Use maven-publish for publishing the Tooling API

This moves all custom configuration code for the shaded binary and

sources JARs into the 'ShadedJarPlugin' and the configuration of

publication into the 'publish-public-libraries' plugin.

The tooling-api project is currently the only project using these

two plugins.

    • -71
    • +0
    ./plugins/publish/ArtifactPatternTest.kt
  1. … 15 more files in changeset.
Use maven-publish for publishing the Tooling API

This moves all custom configuration code for the shaded binary and

sources JARs into the 'ShadedJarPlugin' and the configuration of

publication into the 'publish-public-libraries' plugin.

The tooling-api project is currently the only project using these

two plugins.

    • -71
    • +0
    ./plugins/publish/ArtifactPatternTest.kt
  1. … 12 more files in changeset.
Use maven-publish for publishing the Tooling API

This moves all custom configuration code for the shaded binary and

sources JARs into the 'ShadedJarPlugin' and the configuration of

publication into the 'publish-public-libraries' plugin.

The tooling-api project is currently the only project using these

two plugins.

    • -71
    • +0
    ./plugins/publish/ArtifactPatternTest.kt
  1. … 15 more files in changeset.
Use maven-publish for publishing the Tooling API

This moves all custom configuration code for the shaded binary and

sources JARs into the 'ShadedJarPlugin' and the configuration of

publication into the 'publish-public-libraries' plugin.

The tooling-api project is currently the only project using these

two plugins.

    • -71
    • +0
    ./plugins/publish/ArtifactPatternTest.kt
  1. … 12 more files in changeset.
Use maven-publish for publishing the Tooling API

This moves all custom configuration code for the shaded binary and

sources JARs into the 'ShadedJarPlugin' and the configuration of

publication into the 'publish-public-libraries' plugin.

The tooling-api project is currently the only project using these

two plugins.

    • -71
    • +0
    ./plugins/publish/ArtifactPatternTest.kt
  1. … 13 more files in changeset.
Use maven-publish for publishing the Tooling API

This moves all custom configuration code for the shaded binary and

sources JARs into the 'ShadedJarPlugin' and the configuration of

publication into the 'publish-public-libraries' plugin.

The tooling-api project is currently the only project using these

two plugins.

    • -71
    • +0
    ./plugins/publish/ArtifactPatternTest.kt
  1. … 14 more files in changeset.
Ignore tests

Fix incorrect split (#10689)

I made a mistake when splitting the test sets: suppose we have 1000 tests and want to split into 3 buckets, the previous split is [333,333,333,1], so the test include/exclude patterns are:

- include 1..333

- include 334..666

- exclude 1..999

We're missing a large subset of tests! This fixes this issue by correctly splitting the buckets.

  1. … 2 more files in changeset.
Fix split

  1. … 2 more files in changeset.
Fix BuildTypesPluginTest

Fix BuildTypesPluginTest

Remove debug code

  1. … 1 more file in changeset.
Use defaults

  1. … 1 more file in changeset.
Try latest nightly

  1. … 35 more files in changeset.
Try latest nightly

  1. … 35 more files in changeset.
Ignore DetermineBaselinesTest

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.

    • -0
    • +157
    ./plugins/performance/DetermineBaselinesTest.kt
  1. … 3 more files in changeset.
Use 'repo.gradle.org' as repository URL

    • -1
    • +1
    ./plugins/publish/ArtifactPatternTest.kt
  1. … 1 more file in changeset.
Prepare for Kotlin DSL upgrade with Kotlin 1.2.60-eap-44

- Disable ktlint-convention plugin because it can only run against a

single Kotlin version

- Disambiguate `mock<T> { ... }` calls via `name` parameter

(necessary due to the `SamConversionForKotlinFunctions` feature)

- Replace delegated property of type `Any?` by API call

- Replace calls to reified extensions moved upstream by API calls

  1. … 7 more files in changeset.
Convert `PublishPublicLibrariesPlugin` to precompiled script plugin

    • -0
    • +4
    ./plugins/publish/ArtifactPatternTest.kt
  1. … 4 more files in changeset.
Apply ktlint-convention rules to Kotlin code in buildSrc

    • -1
    • +1
    ./plugins/publish/ArtifactPatternTest.kt
  1. … 55 more files in changeset.