TeamCity Continuous Integration
We use JetBrains TeamCity for various continuous integration and testing tasks. Our instance is available at https://teamcity.cockroachdb.com - you may sign in with your GitHub OAuth credentials.
TeamCity is triggered for each new or updated pull request to this repository. It runs a set of tests triggered by the GitHub CI job and reports the results back to the pull request as a GitHub status check. This job succeeds when all of its dependencies succeed. The tests are as follows:
Each of these is run by a separate build agent in parallel.
TeamCity represents GitHub pull requests by branches named by the number of the pull request.
If tests fail on a pull request due to a flaky test or some other kind of transient error, you can retrigger the tests from TeamCity by running the GitHub CI job against the pull request branch you're trying to rebuild. Make sure to rebuild the GitHub CI job itself and not any of the individual test jobs - those will be automatically triggered when you request a GitHub CI build.
Here's a mini screencast of how to view a test failure and retrigger TeamCity from a failed status check on GitHub:
