buildSrc

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
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.
Use ValidatePlugins in buildSrc (and upgrade wrapper)

  1. … 1 more file in changeset.
Update auto apply scan plugin to 2.4.2 (#10535)

  1. … 2 more files in changeset.
Broken link check as part of sanity check and archive report on CI

  1. … 1 more file in changeset.
Broken link check as part of sanity check and archive report on CI

  1. … 1 more file in changeset.
Revert "Make DistributedPerformanceTest non-abstract"

This reverts commit c7b91fc418865d3660723eb42ea5e749b11651e0.

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.

    • -0
    • +1
    ./subprojects/plugins/plugins.gradle.kts
Fix split

    • -0
    • +1
    ./subprojects/plugins/plugins.gradle.kts
Count test number

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. … 7 more files in changeset.
Resolve feedback

  1. … 6 more files in changeset.
Make DistributedPerformanceTest non-abstract

Seems like the Gradleception build fails when it is abstract...

Make buckets in TeamCity configuration

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

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

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

  1. … 7 more files in changeset.
Remove one level from the JUnitXmlEvents

WorkerSuites seems to be unnecessary.

Remove one level from the JUnitXmlEvents

WorkerSuites seems to be unnecessary.

Add some unit tests

Add some unit tests

Remove unused properties

Remove unused properties

Add Javadoc

Add Javadoc for new methods

Add Javadoc

Move rerun strategy to property

and add some DSL to configure it.

Move rerun strategy to property

and add some DSL to configure it.

The reporter checks for errors

so don't, check in the performance task as well. This worked before

since only the retry task needed to have the "right" outcome.

The reporter checks for errors

so don't, check in the performance task as well. This worked before

since only the retry task needed to have the "right" outcome.