Update Bazel rules repository name
This commit is contained in:
parent
5a07f728c3
commit
371b44dcf2
|
@ -16,7 +16,7 @@ jobs:
|
|||
- name: CHECKOUT bazel-erlang
|
||||
uses: actions/checkout@v2.4.0
|
||||
with:
|
||||
repository: rabbitmq/bazel-erlang
|
||||
repository: rabbitmq/rules_erlang
|
||||
path: bazel-erlang
|
||||
- name: DETERMINE LATEST COMMIT
|
||||
id: find-commit
|
||||
|
|
2
BAZEL.md
2
BAZEL.md
|
@ -9,7 +9,7 @@ RabbitMQ, Tier1 plugins included, is a large codebase. The developer experience
|
|||
|
||||
More importantly, RabbitMQ's test suite is large and takes hours if run on a single machine. Bazel allows tests to be run in parallel on a large number of remote workers if needed, and furthermore uses cached test results when branches of the codebase remain unchanged.
|
||||
|
||||
Bazel does not provide built in Erlang or Elixir support, nor is there an available library of bazel rules. Therefore, we have defined our own rules in https://github.com/rabbitmq/bazel-erlang. Elixir compilation is handled as a special case within this repository. To use these rules, the location of your Erlang and Elixir installations must be indicated to the build (see below).
|
||||
Bazel does not provide built in Erlang or Elixir support, nor is there an available library of bazel rules. Therefore, we have defined our own rules in https://github.com/rabbitmq/rules_erlang. Elixir compilation is handled as a special case within this repository. To use these rules, the location of your Erlang and Elixir installations must be indicated to the build (see below).
|
||||
|
||||
While most of work for running tests happens in Bazel, the suite still makes use of some external tools for commands, notably gnu `make` and `openssl`. Ideally we could bring all of these tools under bazel, so that the only tool needed would be `bazel` or `bazelisk`, but that will take some time.
|
||||
|
||||
|
|
|
@ -60,7 +60,7 @@ rules_pkg_dependencies()
|
|||
git_repository(
|
||||
name = "bazel-erlang",
|
||||
commit = "d62a13548b3d1e5bd2830f42e3f3933ae17db3cb",
|
||||
remote = "https://github.com/rabbitmq/bazel-erlang.git",
|
||||
remote = "https://github.com/rabbitmq/rules_erlang.git",
|
||||
)
|
||||
|
||||
load("@bazel-erlang//:bazel_erlang.bzl", "bazel_erlang_deps")
|
||||
|
|
|
@ -149,7 +149,7 @@ consistent release schedule.
|
|||
|
||||
* Continuous integration of open source RabbitMQ has switched to Bazel, GitHub Actions and [BuildBuddy](https://buildbuddy.io), resulting in much faster and incremental test runs.
|
||||
|
||||
[Bazel support for Erlang](https://github.com/rabbitmq/bazel-erlang) is a new project open sourced by the RabbitMQ Core team as a result.
|
||||
[Bazel support for Erlang](https://github.com/rabbitmq/rules_erlang) is a new project open sourced by the RabbitMQ Core team as a result.
|
||||
|
||||
* Process group membership now uses `pg`.
|
||||
|
||||
|
|
Loading…
Reference in New Issue