This commit uses the correct property name (`prettier` vs `pretter`) to check whether prettier is enabled via the config. (It also fixes some typos in `dev-infra`.) PR Close #41860
39 lines
1.7 KiB
Python
39 lines
1.7 KiB
Python
package(default_visibility = ["//visibility:public"])
|
|
|
|
platform(
|
|
name = "platform",
|
|
constraint_values = [
|
|
"@bazel_tools//platforms:linux",
|
|
"@bazel_tools//platforms:x86_64",
|
|
"@bazel_tools//tools/cpp:clang",
|
|
],
|
|
# We use a basic docker image from the Google Cloud container registry that supports
|
|
# browser tests. Note that we usually do not use any of the local browsers, but the image
|
|
# guarantees that necessary dependencies for launching browsers are installed. Since we
|
|
# do not rely on many binaries/tools from the image, the image doesn't need to be updated
|
|
# frequently. There are rare cases where it needs to be updated. e.g. for a more recent Bash
|
|
# version, or new system settings that are required for launching browsers. In order to do that,
|
|
# we need to either see if the `rbe-ubuntu16-04-webtest` image can be updated, or if we need to
|
|
# build and publish our own image to the Google cloud image registry. Additionally, we set the
|
|
# `SYS_ADMIN` capability so that browsers can be launched with sandbox mode enabled. Related
|
|
# information: https://developers.google.com/web/tools/puppeteer/troubleshooting#running_puppeteer_in_docker
|
|
remote_execution_properties = """
|
|
properties: {
|
|
name: "container-image"
|
|
value:"docker://gcr.io/cloud-marketplace/google/rbe-ubuntu16-04-webtest@sha256:886a12dc4726f5b991b46386292afa8d943b6703a5496c8a1e07cfde778d9044"
|
|
}
|
|
properties: {
|
|
name: "dockerAddCapabilities"
|
|
value: "SYS_ADMIN"
|
|
}
|
|
""",
|
|
)
|
|
|
|
filegroup(
|
|
name = "files",
|
|
srcs = [
|
|
"BUILD.bazel",
|
|
"//dev-infra/bazel/remote-execution/cpp:files",
|
|
],
|
|
)
|