FunctionalTest.kt

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Automate bucket generation

  1. … 16 more files in changeset.
Fix buckets

  1. … 5 more files in changeset.
Automate bucket generation

  1. … 16 more files in changeset.
Automate bucket generation

  1. … 16 more files in changeset.
Automate bucket generation

  1. … 16 more files in changeset.
Set OS specific Android home

  1. … 4 more files in changeset.
Add ANDROID_HOME on mac agents as well

Add `ANDROID_HOME` for Windows

Add `ANDROID_HOME` for Windows

Make more buckets (#10765)

* Make more buckets

* Put project name in bucket name

* Refactor & add tests

* Fix warnings

  1. … 5 more files in changeset.
Refactor & add tests

  1. … 4 more files in changeset.
Put project name in bucket name

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.
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.
Simplify map chain

Use fewer parallel forks on macOS

since the agents are not very powerful.

Use fewer parallel forks on macOS

since the agents are not very powerful.

Merge build types running only unit tests (#9895)

Merging again now that build types can be invoked for subprojects.

This reverts commit 4636d4f056b108ae70e9600c0a111018b292ddfe.

  1. … 6 more files in changeset.
Revert "Merge build types running only unit tests (#9895)"

Looks like build types only work for the first project.

This reverts commit 99a6b64eea4f9bfa6a06969368b2c7c680e5cb6d.

  1. … 6 more files in changeset.
Merge build types running only unit tests (#9895)

So we don't have so many small build types. The unit tests should run

very fast anyway.

  1. … 6 more files in changeset.
Automatically format code

  1. … 15 more files in changeset.
Automatically format code

  1. … 15 more files in changeset.
Merge build types running only unit tests

So we don't have so many small build types. The unit tests should run

very fast anyway.

  1. … 6 more files in changeset.
Move Kotlin DSL code to settings

  1. … 99 more files in changeset.
Use the same exact TeamCity build configuration from master

  1. … 61 more files in changeset.
Extract common build logic

  1. … 20 more files in changeset.