root
/
rabbitmq-server
mirror of https://github.com/rabbitmq/rabbitmq-server.git
1
0
Fork 0
Code Issues Actions 8 Packages Projects Releases Wiki Activity
rabbitmq-server/WORKSPACE

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

51 lines
1.4 KiB
Python
Raw Normal View History

Use pkg_files rules to avoid extra tars in package-generic-unix and source_archive macros
2023-03-03 19:02:02 +08:00
workspace(name = "rabbitmq-server")
Use gazelle for external erlang deps (#6935) * Add gazelle for use with update-repos command * Use explicit BUILD.app_name files for erlang app deps This allows us to remove the duplicate definitions in workspace_helpers.bzl These files are generated with gazelle. For instance: BUILD.ra is generated with `bazel run gazelle -- update-repos --verbose --build_files_dir=bazel hex.pm/ra@2.4.6` Running gazelle this way will modify the WORKSPACE file, as gazelle does not yet support MODULE.bazel files. Such changes to the WORKSPACE can be dropped, and should not be committed. It may also update the `moduleindex.yaml` file. Changes to `moduleindex.yaml` should be committed. However * skip the explicit bazel/BUILD.osiris file, as osiris already contains the file in its repo * skip the explict BUILD.inet_tcp_proxy_dist file, since the repo already contains a bazel BUILD.bazel file gazelle command: `bazel run gazelle -- update-repos --verbose --build_files_dir=bazel inet_tcp_proxy_dist=github.com/rabbitmq/inet_tcp_proxy@master` * jose is imported with `bazel run gazelle -- update-repos --verbose --build_files_dir=bazel jose=github.com/michaelklishin/erlang-jose@d63c1c5c8f9c1a4f1438e234b886de8607a0034e` * Move the bats dep directly to WORKSPACE, drop workspace_helpers.bzl * Use bzlmod in windows tests
2023-01-25 16:41:56 +08:00
load("@bazel_tools//tools/build_defs/repo:git.bzl", "git_repository", "new_git_repository")
Adopt otp 26.1.2
2024-03-27 18:24:05 +08:00
load("@bazel_tools//tools/build_defs/repo:http.bzl", "http_archive", "http_file")
Make rabbitmq-server work with rules_erlang 3 Also rework elixir dependency handling, so we no longer rely on mix to fetch the rabbitmq_cli deps Also: - Specify ra version with a commit rather than a branch - Fixup compilation options for erlang 23 - Add missing ra reference in MODULE.bazel - Add missing flag in oci.yaml - Reduce bazel rbe jobs to try to save memory - Use bazel built erlang for erlang git master tests - Use the same cache for all the workflows but windows - Avoid using `mix local.hex --force` in elixir rules - Fetching seems blocked in CI, and this should reduce hex api usage in all builds, which is always nice - Remove xref and dialyze tags since rules_erlang 3 includes them in the defaults
2022-05-17 20:07:16 +08:00
Update rules_pkg to 0.9.1
2023-05-12 15:26:13 +08:00
http_archive(
name = "rules_pkg",
rules_pkg 0.9.1 -> 0.10.1 (#10736) * rules_pkg 0.9.1 -> 0.10.1
2024-03-14 22:17:50 +08:00
sha256 = "d250924a2ecc5176808fc4c25d5cf5e9e79e6346d79d5ab1c493e289e722d1d0",
Update rules_pkg to 0.9.1
2023-05-12 15:26:13 +08:00
urls = [
rules_pkg 0.9.1 -> 0.10.1 (#10736) * rules_pkg 0.9.1 -> 0.10.1
2024-03-14 22:17:50 +08:00
"https://mirror.bazel.build/github.com/bazelbuild/rules_pkg/releases/download/0.10.1/rules_pkg-0.10.1.tar.gz",
"https://github.com/bazelbuild/rules_pkg/releases/download/0.10.1/rules_pkg-0.10.1.tar.gz",
Update rules_pkg to 0.9.1
2023-05-12 15:26:13 +08:00
],
)
load("@rules_pkg//:deps.bzl", "rules_pkg_dependencies")
rules_pkg_dependencies()
Use gazelle for external erlang deps (#6935) * Add gazelle for use with update-repos command * Use explicit BUILD.app_name files for erlang app deps This allows us to remove the duplicate definitions in workspace_helpers.bzl These files are generated with gazelle. For instance: BUILD.ra is generated with `bazel run gazelle -- update-repos --verbose --build_files_dir=bazel hex.pm/ra@2.4.6` Running gazelle this way will modify the WORKSPACE file, as gazelle does not yet support MODULE.bazel files. Such changes to the WORKSPACE can be dropped, and should not be committed. It may also update the `moduleindex.yaml` file. Changes to `moduleindex.yaml` should be committed. However * skip the explicit bazel/BUILD.osiris file, as osiris already contains the file in its repo * skip the explict BUILD.inet_tcp_proxy_dist file, since the repo already contains a bazel BUILD.bazel file gazelle command: `bazel run gazelle -- update-repos --verbose --build_files_dir=bazel inet_tcp_proxy_dist=github.com/rabbitmq/inet_tcp_proxy@master` * jose is imported with `bazel run gazelle -- update-repos --verbose --build_files_dir=bazel jose=github.com/michaelklishin/erlang-jose@d63c1c5c8f9c1a4f1438e234b886de8607a0034e` * Move the bats dep directly to WORKSPACE, drop workspace_helpers.bzl * Use bzlmod in windows tests
2023-01-25 16:41:56 +08:00
git_repository(
name = "rules_erlang",
remote = "https://github.com/rabbitmq/rules_erlang.git",
Use rules_erlang 3.15.1
2024-03-27 19:46:10 +08:00
tag = "3.15.1",
Make rabbitmq-server work with rules_erlang 3 Also rework elixir dependency handling, so we no longer rely on mix to fetch the rabbitmq_cli deps Also: - Specify ra version with a commit rather than a branch - Fixup compilation options for erlang 23 - Add missing ra reference in MODULE.bazel - Add missing flag in oci.yaml - Reduce bazel rbe jobs to try to save memory - Use bazel built erlang for erlang git master tests - Use the same cache for all the workflows but windows - Avoid using `mix local.hex --force` in elixir rules - Fetching seems blocked in CI, and this should reduce hex api usage in all builds, which is always nice - Remove xref and dialyze tags since rules_erlang 3 includes them in the defaults
2022-05-17 20:07:16 +08:00
)
Use gazelle for external erlang deps (#6935) * Add gazelle for use with update-repos command * Use explicit BUILD.app_name files for erlang app deps This allows us to remove the duplicate definitions in workspace_helpers.bzl These files are generated with gazelle. For instance: BUILD.ra is generated with `bazel run gazelle -- update-repos --verbose --build_files_dir=bazel hex.pm/ra@2.4.6` Running gazelle this way will modify the WORKSPACE file, as gazelle does not yet support MODULE.bazel files. Such changes to the WORKSPACE can be dropped, and should not be committed. It may also update the `moduleindex.yaml` file. Changes to `moduleindex.yaml` should be committed. However * skip the explicit bazel/BUILD.osiris file, as osiris already contains the file in its repo * skip the explict BUILD.inet_tcp_proxy_dist file, since the repo already contains a bazel BUILD.bazel file gazelle command: `bazel run gazelle -- update-repos --verbose --build_files_dir=bazel inet_tcp_proxy_dist=github.com/rabbitmq/inet_tcp_proxy@master` * jose is imported with `bazel run gazelle -- update-repos --verbose --build_files_dir=bazel jose=github.com/michaelklishin/erlang-jose@d63c1c5c8f9c1a4f1438e234b886de8607a0034e` * Move the bats dep directly to WORKSPACE, drop workspace_helpers.bzl * Use bzlmod in windows tests
2023-01-25 16:41:56 +08:00
load("@rules_erlang//:internal_deps.bzl", "rules_erlang_internal_deps")
Make rabbitmq-server work with rules_erlang 3 Also rework elixir dependency handling, so we no longer rely on mix to fetch the rabbitmq_cli deps Also: - Specify ra version with a commit rather than a branch - Fixup compilation options for erlang 23 - Add missing ra reference in MODULE.bazel - Add missing flag in oci.yaml - Reduce bazel rbe jobs to try to save memory - Use bazel built erlang for erlang git master tests - Use the same cache for all the workflows but windows - Avoid using `mix local.hex --force` in elixir rules - Fetching seems blocked in CI, and this should reduce hex api usage in all builds, which is always nice - Remove xref and dialyze tags since rules_erlang 3 includes them in the defaults
2022-05-17 20:07:16 +08:00
Use gazelle for external erlang deps (#6935) * Add gazelle for use with update-repos command * Use explicit BUILD.app_name files for erlang app deps This allows us to remove the duplicate definitions in workspace_helpers.bzl These files are generated with gazelle. For instance: BUILD.ra is generated with `bazel run gazelle -- update-repos --verbose --build_files_dir=bazel hex.pm/ra@2.4.6` Running gazelle this way will modify the WORKSPACE file, as gazelle does not yet support MODULE.bazel files. Such changes to the WORKSPACE can be dropped, and should not be committed. It may also update the `moduleindex.yaml` file. Changes to `moduleindex.yaml` should be committed. However * skip the explicit bazel/BUILD.osiris file, as osiris already contains the file in its repo * skip the explict BUILD.inet_tcp_proxy_dist file, since the repo already contains a bazel BUILD.bazel file gazelle command: `bazel run gazelle -- update-repos --verbose --build_files_dir=bazel inet_tcp_proxy_dist=github.com/rabbitmq/inet_tcp_proxy@master` * jose is imported with `bazel run gazelle -- update-repos --verbose --build_files_dir=bazel jose=github.com/michaelklishin/erlang-jose@d63c1c5c8f9c1a4f1438e234b886de8607a0034e` * Move the bats dep directly to WORKSPACE, drop workspace_helpers.bzl * Use bzlmod in windows tests
2023-01-25 16:41:56 +08:00
rules_erlang_internal_deps()
Add a partial Bazel build (#2938) Adds WORKSPACE.bazel, BUILD.bazel & *.bzl files for partial build & test with Bazel. Introduces a build-time dependency on https://github.com/rabbitmq/bazel-erlang
2021-03-29 17:01:43 +08:00
Use gazelle for external erlang deps (#6935) * Add gazelle for use with update-repos command * Use explicit BUILD.app_name files for erlang app deps This allows us to remove the duplicate definitions in workspace_helpers.bzl These files are generated with gazelle. For instance: BUILD.ra is generated with `bazel run gazelle -- update-repos --verbose --build_files_dir=bazel hex.pm/ra@2.4.6` Running gazelle this way will modify the WORKSPACE file, as gazelle does not yet support MODULE.bazel files. Such changes to the WORKSPACE can be dropped, and should not be committed. It may also update the `moduleindex.yaml` file. Changes to `moduleindex.yaml` should be committed. However * skip the explicit bazel/BUILD.osiris file, as osiris already contains the file in its repo * skip the explict BUILD.inet_tcp_proxy_dist file, since the repo already contains a bazel BUILD.bazel file gazelle command: `bazel run gazelle -- update-repos --verbose --build_files_dir=bazel inet_tcp_proxy_dist=github.com/rabbitmq/inet_tcp_proxy@master` * jose is imported with `bazel run gazelle -- update-repos --verbose --build_files_dir=bazel jose=github.com/michaelklishin/erlang-jose@d63c1c5c8f9c1a4f1438e234b886de8607a0034e` * Move the bats dep directly to WORKSPACE, drop workspace_helpers.bzl * Use bzlmod in windows tests
2023-01-25 16:41:56 +08:00
load("@rules_erlang//:internal_setup.bzl", "rules_erlang_internal_setup")
rules_erlang_internal_setup(go_repository_default_config = "//:WORKSPACE")
Add the bazel target :package-generic-unix Which can be used to build the artifact with bazel
2021-09-30 21:49:08 +08:00
Use gazelle for external erlang deps (#6935) * Add gazelle for use with update-repos command * Use explicit BUILD.app_name files for erlang app deps This allows us to remove the duplicate definitions in workspace_helpers.bzl These files are generated with gazelle. For instance: BUILD.ra is generated with `bazel run gazelle -- update-repos --verbose --build_files_dir=bazel hex.pm/ra@2.4.6` Running gazelle this way will modify the WORKSPACE file, as gazelle does not yet support MODULE.bazel files. Such changes to the WORKSPACE can be dropped, and should not be committed. It may also update the `moduleindex.yaml` file. Changes to `moduleindex.yaml` should be committed. However * skip the explicit bazel/BUILD.osiris file, as osiris already contains the file in its repo * skip the explict BUILD.inet_tcp_proxy_dist file, since the repo already contains a bazel BUILD.bazel file gazelle command: `bazel run gazelle -- update-repos --verbose --build_files_dir=bazel inet_tcp_proxy_dist=github.com/rabbitmq/inet_tcp_proxy@master` * jose is imported with `bazel run gazelle -- update-repos --verbose --build_files_dir=bazel jose=github.com/michaelklishin/erlang-jose@d63c1c5c8f9c1a4f1438e234b886de8607a0034e` * Move the bats dep directly to WORKSPACE, drop workspace_helpers.bzl * Use bzlmod in windows tests
2023-01-25 16:41:56 +08:00
load("@rules_erlang//gazelle:deps.bzl", "gazelle_deps")
Add the bazel target :package-generic-unix Which can be used to build the artifact with bazel
2021-09-30 21:49:08 +08:00
Use gazelle for external erlang deps (#6935) * Add gazelle for use with update-repos command * Use explicit BUILD.app_name files for erlang app deps This allows us to remove the duplicate definitions in workspace_helpers.bzl These files are generated with gazelle. For instance: BUILD.ra is generated with `bazel run gazelle -- update-repos --verbose --build_files_dir=bazel hex.pm/ra@2.4.6` Running gazelle this way will modify the WORKSPACE file, as gazelle does not yet support MODULE.bazel files. Such changes to the WORKSPACE can be dropped, and should not be committed. It may also update the `moduleindex.yaml` file. Changes to `moduleindex.yaml` should be committed. However * skip the explicit bazel/BUILD.osiris file, as osiris already contains the file in its repo * skip the explict BUILD.inet_tcp_proxy_dist file, since the repo already contains a bazel BUILD.bazel file gazelle command: `bazel run gazelle -- update-repos --verbose --build_files_dir=bazel inet_tcp_proxy_dist=github.com/rabbitmq/inet_tcp_proxy@master` * jose is imported with `bazel run gazelle -- update-repos --verbose --build_files_dir=bazel jose=github.com/michaelklishin/erlang-jose@d63c1c5c8f9c1a4f1438e234b886de8607a0034e` * Move the bats dep directly to WORKSPACE, drop workspace_helpers.bzl * Use bzlmod in windows tests
2023-01-25 16:41:56 +08:00
gazelle_deps()
Add the bazel target :package-generic-unix Which can be used to build the artifact with bazel
2021-09-30 21:49:08 +08:00
Use gazelle for external erlang deps (#6935) * Add gazelle for use with update-repos command * Use explicit BUILD.app_name files for erlang app deps This allows us to remove the duplicate definitions in workspace_helpers.bzl These files are generated with gazelle. For instance: BUILD.ra is generated with `bazel run gazelle -- update-repos --verbose --build_files_dir=bazel hex.pm/ra@2.4.6` Running gazelle this way will modify the WORKSPACE file, as gazelle does not yet support MODULE.bazel files. Such changes to the WORKSPACE can be dropped, and should not be committed. It may also update the `moduleindex.yaml` file. Changes to `moduleindex.yaml` should be committed. However * skip the explicit bazel/BUILD.osiris file, as osiris already contains the file in its repo * skip the explict BUILD.inet_tcp_proxy_dist file, since the repo already contains a bazel BUILD.bazel file gazelle command: `bazel run gazelle -- update-repos --verbose --build_files_dir=bazel inet_tcp_proxy_dist=github.com/rabbitmq/inet_tcp_proxy@master` * jose is imported with `bazel run gazelle -- update-repos --verbose --build_files_dir=bazel jose=github.com/michaelklishin/erlang-jose@d63c1c5c8f9c1a4f1438e234b886de8607a0034e` * Move the bats dep directly to WORKSPACE, drop workspace_helpers.bzl * Use bzlmod in windows tests
2023-01-25 16:41:56 +08:00
new_git_repository(
name = "bats",
build_file = "@//:BUILD.bats",
remote = "https://github.com/sstephenson/bats",
tag = "v0.4.0",
)
Add a partial Bazel build (#2938) Adds WORKSPACE.bazel, BUILD.bazel & *.bzl files for partial build & test with Bazel. Introduces a build-time dependency on https://github.com/rabbitmq/bazel-erlang
2021-03-29 17:01:43 +08:00
load("//deps/amqp10_client:activemq.bzl", "activemq_archive")
activemq_archive()
Mixed version testing in bazel (#3200) Unlike with gnu make, mixed version testing with bazel uses a package-generic-unix for the secondary umbrella rather than the source. This brings the benefit of being able to mixed version test releases built with older erlang versions (even though all nodes will run under the single version given to bazel) This introduces new test labels, adding a `-mixed` suffix for every existing test. They can be skipped if necessary with `--test_tag_filters` (see the github actions workflow for an example) As part of the change, it is now possible to run an old release of rabbit with rabbitmq_run rule, such as: `bazel run @rabbitmq-server-generic-unix-3.8.17//:rabbitmq-run run-broker`
2021-07-19 20:33:25 +08:00
Fetch the secondary umbrella via the module system to avoid repo_mapping with a hard coded version of rules_erlang
2022-06-24 17:16:08 +08:00
load("//bazel/bzlmod:secondary_umbrella.bzl", "secondary_umbrella")
Mixed version testing in bazel (#3200) Unlike with gnu make, mixed version testing with bazel uses a package-generic-unix for the secondary umbrella rather than the source. This brings the benefit of being able to mixed version test releases built with older erlang versions (even though all nodes will run under the single version given to bazel) This introduces new test labels, adding a `-mixed` suffix for every existing test. They can be skipped if necessary with `--test_tag_filters` (see the github actions workflow for an example) As part of the change, it is now possible to run an old release of rabbit with rabbitmq_run rule, such as: `bazel run @rabbitmq-server-generic-unix-3.8.17//:rabbitmq-run run-broker`
2021-07-19 20:33:25 +08:00
Fetch the secondary umbrella via the module system to avoid repo_mapping with a hard coded version of rules_erlang
2022-06-24 17:16:08 +08:00
secondary_umbrella()