[
    {
        "variation": "linux",
        "configurations": [
            {"node": "linux-x86_64"},
            {"node": "ubuntu_16.04-x86_64"}
        ],
        "parameters": {
            "configure": ["$BAZEL run @yarn//:yarn"],
            "test_tag_filters": ["-browser:Chrome"]
        }
    },
    {
        "variation": "mac",
        "configurations": [
            {"node": "darwin-x86_64"}
        ],
        "parameters": {
            "configure": ["$BAZEL run @yarn//:yarn"],
        }
    }
]

Introduce a config file for ci.bazel.build
Introduce a config file for ci.bazel.build

This is the CI that ensures upstream Bazel changes don't break the TypeScript rules.

This is live only after https://github.com/bazelbuild/continuous-integration/pull/162 is merged.

We need to exclude Chrome browser tests on linux because the ci.bazel.build apparently doesn't include that binary on the image, see eg. https://ci.bazel.io/blue/organizations/jenkins/PR%2Frules_typescript/detail/rules_typescript/122/pipeline

PiperOrigin-RevId: 179665055
