summaryrefslogtreecommitdiff
path: root/BAZEL.md
diff options
context:
space:
mode:
authorMichael Klishin <michael@clojurewerkz.org>2022-01-05 19:06:37 +0300
committerMichael Klishin <michael@clojurewerkz.org>2022-01-05 19:06:37 +0300
commit7787fe2780b203bdc314751418c96276d3beb0b1 (patch)
tree9733ee6ece4ff8d1d2ab231670019a2c87c391de /BAZEL.md
parent371b44dcf2ce4b0909e8b1d0255cd9a815f135d3 (diff)
downloadrabbitmq-server-git-7787fe2780b203bdc314751418c96276d3beb0b1.tar.gz
Revert "Update Bazel rules repository name"
This reverts commit 371b44dcf2ce4b0909e8b1d0255cd9a815f135d3.
Diffstat (limited to 'BAZEL.md')
-rw-r--r--BAZEL.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/BAZEL.md b/BAZEL.md
index 20569e2e67..9ab05a12cf 100644
--- a/BAZEL.md
+++ b/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/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).
+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).
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.