MORPH
SIGN IN SIGN UP
ray-project / ray UNCLAIMED

Ray is an AI compute engine. Ray consists of a core distributed runtime and a set of AI Libraries for accelerating ML workloads.

0 0 1 Python
Normal View History Raw
Bazel move more shell to native rules (#9314) Co-authored-by: Mehrdad <noreply@github.com>
2020-07-09 09:02:35 -07:00
load("@bazel_skylib//:workspace.bzl", "bazel_skylib_workspace")
[ci] Shorten bazel directory paths to avoid failures on Windows (#55525) - Shortening bazel workspace name: `s/com_github_ray_project_ray/io_ray` - Set `--output_base=c:/bzl` instead of `--output_user_root=c:/raytmp`, which saves ~20 characters in the path. --------- Signed-off-by: Edward Oakes <ed.nmi.oakes@gmail.com>
2025-08-12 21:17:48 -04:00
load("@io_ray//java:dependencies.bzl", "gen_java_deps")
[Bazel] Modifying WORKSPACE file, so that you can make the project used as a thirdparty project (#4711) * Modifying WORKSPACE file, so that you can make the project used as a thirdparty * Modifying WORKSPACE file, so that you can make the project used as a thirdparty * add some files * modify some repositories * modify the name of 'ray_deps_build_all'
2019-04-29 13:02:49 +08:00
load("@com_github_nelhage_rules_boost//:boost/boost.bzl", "boost_deps")
Patch prometheus-cpp internally (#6281)
2019-11-26 14:49:24 -08:00
load("@com_github_jupp0r_prometheus_cpp//bazel:repositories.bzl", "prometheus_cpp_repositories")
Use GRCP and Bazel 1.0 (#6002)
2019-11-08 15:58:28 -08:00
load("@com_github_grpc_grpc//third_party/py:python_configure.bzl", "python_configure")
[gRPC] Use gRPC for inter-node-manager communication (#4968)
2019-06-17 19:00:50 +08:00
load("@com_github_grpc_grpc//bazel:grpc_deps.bzl", "grpc_deps")
Use GRCP and Bazel 1.0 (#6002)
2019-11-08 15:58:28 -08:00
load("@rules_proto_grpc//:repositories.bzl", "rules_proto_grpc_toolchains")
[Java] Shade some widely used dependencies in bazel_jar_jar rule. (#21237) These dependencies are widely used: - com.google.common - com.google.protobuf - com.google.thirdparty So that we need to shade them to avoid being conflict with jars introduced by user. In this PR, we introduce a `bazel_jar_jar` rule for doing these and also shade them in maven pom files.
2021-12-23 16:54:31 +08:00
load("@com_github_johnynek_bazel_jar_jar//:jar_jar.bzl", "jar_jar_repositories")
Revert "Revert "Revert "Revert "[core] Support encrypted redis connection." (#28991)""" (#29109) Reverts #29078 There are two issues: tsan fail and mac build fail. For TSAN, if we build redis + openssl with tsan the redis will segfault. So we exclude the redis target from the tsan build. For mac failure, the root cause is that in the CI somehow the toolchain picked in rules_foreign_cc is wrong. Failed to find any useful solution within a day. So just use the old build for mac and pick in the runtime. Since redis is only used for testing, win/mac/linux both support rediss.
2022-10-07 04:21:02 +00:00
load("@rules_foreign_cc//foreign_cc:repositories.bzl", "rules_foreign_cc_dependencies")
load("@rules_foreign_cc_thirdparty//openssl:openssl_setup.bzl", "openssl_setup")
[gRPC] Use gRPC for inter-node-manager communication (#4968)
2019-06-17 19:00:50 +08:00
[Bazel] Modifying WORKSPACE file, so that you can make the project used as a thirdparty project (#4711) * Modifying WORKSPACE file, so that you can make the project used as a thirdparty * Modifying WORKSPACE file, so that you can make the project used as a thirdparty * add some files * modify some repositories * modify the name of 'ray_deps_build_all'
2019-04-29 13:02:49 +08:00
def ray_deps_build_all():
Bazel move more shell to native rules (#9314) Co-authored-by: Mehrdad <noreply@github.com>
2020-07-09 09:02:35 -07:00
bazel_skylib_workspace()
[Bazel] Modifying WORKSPACE file, so that you can make the project used as a thirdparty project (#4711) * Modifying WORKSPACE file, so that you can make the project used as a thirdparty * Modifying WORKSPACE file, so that you can make the project used as a thirdparty * add some files * modify some repositories * modify the name of 'ray_deps_build_all'
2019-04-29 13:02:49 +08:00
gen_java_deps()
boost_deps()
prometheus_cpp_repositories()
python_configure(name = "local_config_python")
[gRPC] Use gRPC for inter-node-manager communication (#4968)
2019-06-17 19:00:50 +08:00
grpc_deps()
Use GRCP and Bazel 1.0 (#6002)
2019-11-08 15:58:28 -08:00
rules_proto_grpc_toolchains()
[Java] Shade some widely used dependencies in bazel_jar_jar rule. (#21237) These dependencies are widely used: - com.google.common - com.google.protobuf - com.google.thirdparty So that we need to shade them to avoid being conflict with jars introduced by user. In this PR, we introduce a `bazel_jar_jar` rule for doing these and also shade them in maven pom files.
2021-12-23 16:54:31 +08:00
jar_jar_repositories()
Revert "Revert "Revert "Revert "[core] Support encrypted redis connection." (#28991)""" (#29109) Reverts #29078 There are two issues: tsan fail and mac build fail. For TSAN, if we build redis + openssl with tsan the redis will segfault. So we exclude the redis target from the tsan build. For mac failure, the root cause is that in the CI somehow the toolchain picked in rules_foreign_cc is wrong. Failed to find any useful solution within a day. So just use the old build for mac and pick in the runtime. Since redis is only used for testing, win/mac/linux both support rediss.
2022-10-07 04:21:02 +00:00
rules_foreign_cc_dependencies()
openssl_setup()
Reference in New Issue Copy Permalink