mirror of
https://github.com/angular/angular-cli.git
synced 2025-05-14 17:43:52 +08:00
83 lines
3.6 KiB
Python
83 lines
3.6 KiB
Python
workspace(
|
|
name = "angular_cli",
|
|
managed_directories = {"@npm": ["node_modules"]},
|
|
)
|
|
|
|
load("@bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")
|
|
|
|
http_archive(
|
|
name = "build_bazel_rules_nodejs",
|
|
sha256 = "55a25a762fcf9c9b88ab54436581e671bc9f4f523cb5a1bd32459ebec7be68a8",
|
|
urls = ["https://github.com/bazelbuild/rules_nodejs/releases/download/3.2.2/rules_nodejs-3.2.2.tar.gz"],
|
|
)
|
|
|
|
# Check the bazel version and download npm dependencies
|
|
load("@build_bazel_rules_nodejs//:index.bzl", "check_bazel_version", "check_rules_nodejs_version", "node_repositories", "yarn_install")
|
|
|
|
# Bazel version must be at least the following version because:
|
|
# - 0.26.0 managed_directories feature added which is required for nodejs rules 0.30.0
|
|
# - 0.27.0 has a fix for managed_directories after `rm -rf node_modules`
|
|
check_bazel_version(
|
|
message = """
|
|
You no longer need to install Bazel on your machine.
|
|
Angular has a dependency on the @bazel/bazelisk package which supplies it.
|
|
Try running `yarn bazel` instead.
|
|
(If you did run that, check that you've got a fresh `yarn install`)
|
|
""",
|
|
minimum_bazel_version = "4.0.0",
|
|
)
|
|
|
|
check_rules_nodejs_version(minimum_version_string = "2.0.0")
|
|
|
|
# Setup the Node.js toolchain
|
|
node_repositories(
|
|
node_version = "12.20.2",
|
|
package_json = ["//:package.json"],
|
|
yarn_version = "1.22.4",
|
|
)
|
|
|
|
yarn_install(
|
|
name = "npm",
|
|
data = [
|
|
"//:tools/yarn/check-yarn.js",
|
|
],
|
|
package_json = "//:package.json",
|
|
strict_visibility = False, # Needed for ts-api-guardian. More info about this can be found https://github.com/bazelbuild/rules_nodejs/wiki#strict_visibility-on-yarn_install-and-npm_install-now-defaults-true-2199
|
|
yarn_lock = "//:yarn.lock",
|
|
)
|
|
|
|
##########################
|
|
# Remote Execution Setup #
|
|
##########################
|
|
# Bring in bazel_toolchains for RBE setup configuration.
|
|
http_archive(
|
|
name = "bazel_toolchains",
|
|
sha256 = "1adf5db506a7e3c465a26988514cfc3971af6d5b3c2218925cd6e71ee443fc3f",
|
|
strip_prefix = "bazel-toolchains-4.0.0",
|
|
url = "https://github.com/bazelbuild/bazel-toolchains/archive/4.0.0.tar.gz",
|
|
)
|
|
|
|
load("@bazel_toolchains//rules:environments.bzl", "clang_env")
|
|
load("@bazel_toolchains//rules:rbe_repo.bzl", "rbe_autoconfig")
|
|
|
|
rbe_autoconfig(
|
|
name = "rbe_ubuntu1604_angular",
|
|
# Need to specify a base container digest in order to ensure that we can use the checked-in
|
|
# platform configurations for the "ubuntu16_04" image. Otherwise the autoconfig rule would
|
|
# need to pull the image and run it in order determine the toolchain configuration. See:
|
|
# https://github.com/bazelbuild/bazel-toolchains/blob/4.0.0/configs/ubuntu16_04_clang/versions.bzl
|
|
base_container_digest = "sha256:f6568d8168b14aafd1b707019927a63c2d37113a03bcee188218f99bd0327ea1",
|
|
# Note that if you change the `digest`, you might also need to update the
|
|
# `base_container_digest` to make sure marketplace.gcr.io/google/rbe-ubuntu16-04-webtest:<digest>
|
|
# and marketplace.gcr.io/google/rbe-ubuntu16-04:<base_container_digest> have
|
|
# the same Clang and JDK installed. Clang is needed because of the dependency on
|
|
# @com_google_protobuf. Java is needed for the Bazel's test executor Java tool.
|
|
digest = "sha256:f743114235a43355bf8324e2ba0fa6a597236fe06f7bc99aaa9ac703631c306b",
|
|
env = clang_env(),
|
|
registry = "marketplace.gcr.io",
|
|
# We can't use the default "ubuntu16_04" RBE image provided by the autoconfig because we need
|
|
# a specific Linux kernel that comes with "libx11" in order to run headless browser tests.
|
|
repository = "google/rbe-ubuntu16-04-webtest",
|
|
use_checked_in_confs = "Force",
|
|
)
|