Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
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.
Replace password-based authentication with token in distributed performance tests

  1. … 8 more files in changeset.
Replace TeamCityRestBot

  1. … 8 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
    ./src/main/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
    ./src/main/kotlin/org/gradle/gradlebuild/UpdateBranchStatus.kt
  1. … 3 more files in changeset.
Simplify execAndGetStdout

  1. … 1 more file in changeset.
Set a green branch tag when Ready for nightly finishes

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
    ./src/main/kotlin/org/gradle/gradlebuild/UpdateBranchStatus.kt
  1. … 4 more files in changeset.
Fix empty REPO_MIRROR_URLS

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.
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. … 1 more file in changeset.
Fix split

  1. … 1 more file in changeset.
Fix BuildTypesPluginTest

Fix BuildTypesPluginTest

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.
Resolve feedback

  1. … 7 more files in changeset.
Make buckets in TeamCity configuration

  1. … 8 more files in changeset.
Make buckets in TeamCity configuration

  1. … 9 more files in changeset.
Make buckets in TeamCity configuration

  1. … 9 more files in changeset.
Make buckets in TeamCity configuration

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

and add some DSL to configure it.

  1. … 4 more files in changeset.