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

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

148 lines
3.0 KiB
Python
Raw Permalink Normal View History

Use gazelle generated bazel files Bazel build files are now maintained primarily with `bazel run gazelle`. This will analyze and merge changes into the build files as necessitated by certain code changes (e.g. the introduction of new modules). In some cases there hints to gazelle in the build files, such as `# gazelle:erlang...` or `# keep` comments. xref checks on plugins that depend on the cli are a good example.
2023-02-23 21:47:41 +08:00
load("@rules_erlang//:eunit2.bzl", "eunit")
Use the new xref2 macro from rules_erlang That adopts the modern erlang.mk xref behaviour
2022-06-03 18:46:45 +08:00
load("@rules_erlang//:xref2.bzl", "xref")
Use rules_erlang v2 bazel-erlang has been renamed rules_erlang. v2 is a substantial refactor that brings Windows support. While this alone isn't enough to run all rabbitmq-server suites on windows, one can at least now start the broker (bazel run broker) and run the tests that do not start a background broker process
2022-01-06 03:57:48 +08:00
load("@rules_erlang//:dialyze.bzl", "dialyze", "plt")
Fix and refactor amqp_client bazel tests
2021-05-11 02:25:12 +08:00
load("//:rabbitmq_home.bzl", "rabbitmq_home")
load("//:rabbitmq_run.bzl", "rabbitmq_run")
load(
"//:rabbitmq.bzl",
Use improved assert_suites2 macro from rules_erlang 3.9.0
2022-11-24 22:46:08 +08:00
"RABBITMQ_DIALYZER_OPTS",
Also assert no missing suites for all other deps
2021-07-12 23:54:55 +08:00
"assert_suites",
Use rules_erlang v2 bazel-erlang has been renamed rules_erlang. v2 is a substantial refactor that brings Windows support. While this alone isn't enough to run all rabbitmq-server suites on windows, one can at least now start the broker (bazel run broker) and run the tests that do not start a background broker process
2022-01-06 03:57:48 +08:00
"rabbitmq_app",
Fix and refactor amqp_client bazel tests
2021-05-11 02:25:12 +08:00
"rabbitmq_integration_suite",
Bazel file refactoring
2021-05-11 16:44:28 +08:00
"rabbitmq_suite",
Fix and refactor amqp_client bazel tests
2021-05-11 02:25:12 +08:00
)
Use gazelle generated bazel files Bazel build files are now maintained primarily with `bazel run gazelle`. This will analyze and merge changes into the build files as necessitated by certain code changes (e.g. the introduction of new modules). In some cases there hints to gazelle in the build files, such as `# gazelle:erlang...` or `# keep` comments. xref checks on plugins that depend on the cli are a good example.
2023-02-23 21:47:41 +08:00
load(
":app.bzl",
"all_beam_files",
"all_srcs",
"all_test_beam_files",
"test_suite_beam_files",
)
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
APP_ENV = """[
{prefer_ipv6, false},
{ssl_options, []},
{writer_gc_threshold, 1000000000}
]"""
Bring over PROJECT_APP_EXTRA_KEYS values from make to bazel
2022-04-07 23:19:35 +08:00
APP_EXTRA_KEYS = """%% Hex.pm package informations.
{licenses, ["MPL-2.0"]},
{links, [
{"Website", "https://www.rabbitmq.com/"},
Check additional applications when comparing bazel and make results (#8209) * Check additional applications when comparing bazel and make results * Sync bazel/make for amqp_client * Do not fail-fast in build system comparison * promethus -> prometheus * Regenerate BUILD.redbug * When comparing build systems & .app files ignore empty 'registered' It's listed as a required key in https://www.erlang.org/doc/man/app.html, but the same docs state the default is "[]". It seems to ignore it if it's empty. * Copy bazel/BUILD.osiris from BUILD.bazel in the osiris repo Normally it would be generated with `bazel run gazelle-update-repos -- -args osiris@1.5.1=github.com/rabbitmq/osiris@v1.5.1`, but in this case we just want to match it's compilation with erlang.mk with some manual tweaks. * Use elixir 1.15, otherwise mix format fails * Sync bazel/make for rabbitmq_web_dispatch, rabbitmq_management_agent
2023-07-12 23:26:16 +08:00
{"GitHub", "https://github.com/rabbitmq/rabbitmq-server/tree/main/deps/amqp_client"},
Bring over PROJECT_APP_EXTRA_KEYS values from make to bazel
2022-04-07 23:19:35 +08:00
{"User guide", "https://www.rabbitmq.com/erlang-client-user-guide.html"}
]},
{build_tools, ["make", "rebar3"]},
{files, [
"erlang.mk",
"git-revisions.txt",
"include",
"LICENSE*",
"Makefile",
"rabbitmq-components.mk",
"README",
Check additional applications when comparing bazel and make results (#8209) * Check additional applications when comparing bazel and make results * Sync bazel/make for amqp_client * Do not fail-fast in build system comparison * promethus -> prometheus * Regenerate BUILD.redbug * When comparing build systems & .app files ignore empty 'registered' It's listed as a required key in https://www.erlang.org/doc/man/app.html, but the same docs state the default is "[]". It seems to ignore it if it's empty. * Copy bazel/BUILD.osiris from BUILD.bazel in the osiris repo Normally it would be generated with `bazel run gazelle-update-repos -- -args osiris@1.5.1=github.com/rabbitmq/osiris@v1.5.1`, but in this case we just want to match it's compilation with erlang.mk with some manual tweaks. * Use elixir 1.15, otherwise mix format fails * Sync bazel/make for rabbitmq_web_dispatch, rabbitmq_management_agent
2023-07-12 23:26:16 +08:00
"README.md",
"src"
Bring over PROJECT_APP_EXTRA_KEYS values from make to bazel
2022-04-07 23:19:35 +08:00
]}
"""
Use gazelle generated bazel files Bazel build files are now maintained primarily with `bazel run gazelle`. This will analyze and merge changes into the build files as necessitated by certain code changes (e.g. the introduction of new modules). In some cases there hints to gazelle in the build files, such as `# gazelle:erlang...` or `# keep` comments. xref checks on plugins that depend on the cli are a good example.
2023-02-23 21:47:41 +08:00
all_beam_files(name = "all_beam_files")
all_test_beam_files(name = "all_test_beam_files")
all_srcs(name = "all_srcs")
test_suite_beam_files(name = "test_suite_beam_files")
Add dialyze for amqp_client
2021-05-31 16:05:03 +08:00
Use gazelle generated bazel files Bazel build files are now maintained primarily with `bazel run gazelle`. This will analyze and merge changes into the build files as necessitated by certain code changes (e.g. the introduction of new modules). In some cases there hints to gazelle in the build files, such as `# gazelle:erlang...` or `# keep` comments. xref checks on plugins that depend on the cli are a good example.
2023-02-23 21:47:41 +08:00
# gazelle:erlang_app_extra_app xmerl
# gazelle:erlang_app_extra_app ssl
# gazelle:erlang_app_extra_app public_key
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 rules_erlang v2 bazel-erlang has been renamed rules_erlang. v2 is a substantial refactor that brings Windows support. While this alone isn't enough to run all rabbitmq-server suites on windows, one can at least now start the broker (bazel run broker) and run the tests that do not start a background broker process
2022-01-06 03:57:48 +08:00
rabbitmq_app(
Use gazelle generated bazel files Bazel build files are now maintained primarily with `bazel run gazelle`. This will analyze and merge changes into the build files as necessitated by certain code changes (e.g. the introduction of new modules). In some cases there hints to gazelle in the build files, such as `# gazelle:erlang...` or `# keep` comments. xref checks on plugins that depend on the cli are a good example.
2023-02-23 21:47:41 +08:00
name = "erlang_app",
srcs = [":all_srcs"],
hdrs = [":public_hdrs"],
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
app_description = "RabbitMQ AMQP Client",
app_env = APP_ENV,
Bring over PROJECT_APP_EXTRA_KEYS values from make to bazel
2022-04-07 23:19:35 +08:00
app_extra_keys = APP_EXTRA_KEYS,
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
app_module = "amqp_client",
app_name = "amqp_client",
app_registered = [
"amqp_sup",
],
Use gazelle generated bazel files Bazel build files are now maintained primarily with `bazel run gazelle`. This will analyze and merge changes into the build files as necessitated by certain code changes (e.g. the introduction of new modules). In some cases there hints to gazelle in the build files, such as `# gazelle:erlang...` or `# keep` comments. xref checks on plugins that depend on the cli are a good example.
2023-02-23 21:47:41 +08:00
beam_files = [":beam_files"],
extra_apps = [
"xmerl",
"public_key",
"ssl",
],
license_files = [":license_files"],
priv = [":priv"],
deps = [
"//deps/rabbit_common:erlang_app",
"@credentials_obfuscation//:erlang_app",
],
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 generated bazel files Bazel build files are now maintained primarily with `bazel run gazelle`. This will analyze and merge changes into the build files as necessitated by certain code changes (e.g. the introduction of new modules). In some cases there hints to gazelle in the build files, such as `# gazelle:erlang...` or `# keep` comments. xref checks on plugins that depend on the cli are a good example.
2023-02-23 21:47:41 +08:00
xref(
name = "xref",
target = ":erlang_app",
)
Perform xref checks on many tier-1 plugins
2021-05-21 18:02:50 +08:00
Add dialyze for amqp_client
2021-05-31 16:05:03 +08:00
plt(
Use gazelle generated bazel files Bazel build files are now maintained primarily with `bazel run gazelle`. This will analyze and merge changes into the build files as necessitated by certain code changes (e.g. the introduction of new modules). In some cases there hints to gazelle in the build files, such as `# gazelle:erlang...` or `# keep` comments. xref checks on plugins that depend on the cli are a good example.
2023-02-23 21:47:41 +08:00
name = "deps_plt",
for_target = ":erlang_app",
Ignore warnings when building plt files for dependencies As we don't generally care if a dependency has warnings, only the target
2023-04-15 00:22:02 +08:00
ignore_warnings = True,
Use gazelle generated bazel files Bazel build files are now maintained primarily with `bazel run gazelle`. This will analyze and merge changes into the build files as necessitated by certain code changes (e.g. the introduction of new modules). In some cases there hints to gazelle in the build files, such as `# gazelle:erlang...` or `# keep` comments. xref checks on plugins that depend on the cli are a good example.
2023-02-23 21:47:41 +08:00
plt = "//:base_plt",
Add dialyze for amqp_client
2021-05-31 16:05:03 +08:00
)
dialyze(
Use gazelle generated bazel files Bazel build files are now maintained primarily with `bazel run gazelle`. This will analyze and merge changes into the build files as necessitated by certain code changes (e.g. the introduction of new modules). In some cases there hints to gazelle in the build files, such as `# gazelle:erlang...` or `# keep` comments. xref checks on plugins that depend on the cli are a good example.
2023-02-23 21:47:41 +08:00
name = "dialyze",
Fix all dialyzer warnings in `amqp_client` And enable `warnings_as_errors`. A pair of `behaviour_info/1` needed converting to `-callback` directives.
2023-01-13 23:09:57 +08:00
dialyzer_opts = RABBITMQ_DIALYZER_OPTS,
Use gazelle generated bazel files Bazel build files are now maintained primarily with `bazel run gazelle`. This will analyze and merge changes into the build files as necessitated by certain code changes (e.g. the introduction of new modules). In some cases there hints to gazelle in the build files, such as `# gazelle:erlang...` or `# keep` comments. xref checks on plugins that depend on the cli are a good example.
2023-02-23 21:47:41 +08:00
plt = ":deps_plt",
target = ":erlang_app",
Add dialyze for amqp_client
2021-05-31 16:05:03 +08:00
)
Fix and refactor amqp_client bazel tests
2021-05-11 02:25:12 +08:00
rabbitmq_home(
name = "broker-for-tests-home",
plugins = [
Use rules_erlang v2 bazel-erlang has been renamed rules_erlang. v2 is a substantial refactor that brings Windows support. While this alone isn't enough to run all rabbitmq-server suites on windows, one can at least now start the broker (bazel run broker) and run the tests that do not start a background broker process
2022-01-06 03:57:48 +08:00
"//deps/rabbit:erlang_app",
amqp_client system_SUITE apparently needs the cli on the code path I'm not actually sure why the changes to rabbitmqctl compilation necessitated this change, but it seems to be the case
2024-06-17 14:47:53 +08:00
"//deps/rabbitmq_cli:erlang_app",
Fix and refactor amqp_client bazel tests
2021-05-11 02:25:12 +08:00
],
)
rabbitmq_run(
name = "rabbitmq-for-tests-run",
home = ":broker-for-tests-home",
)
Use improved assert_suites2 macro from rules_erlang 3.9.0
2022-11-24 22:46:08 +08:00
rabbitmq_integration_suite(
name = "system_SUITE",
size = "large",
Use gazelle generated bazel files Bazel build files are now maintained primarily with `bazel run gazelle`. This will analyze and merge changes into the build files as necessitated by certain code changes (e.g. the introduction of new modules). In some cases there hints to gazelle in the build files, such as `# gazelle:erlang...` or `# keep` comments. xref checks on plugins that depend on the cli are a good example.
2023-02-23 21:47:41 +08:00
deps = [
Use improved assert_suites2 macro from rules_erlang 3.9.0
2022-11-24 22:46:08 +08:00
"@meck//:erlang_app",
],
)
rabbitmq_suite(
name = "unit_SUITE",
size = "small",
deps = [
Use gazelle generated bazel files Bazel build files are now maintained primarily with `bazel run gazelle`. This will analyze and merge changes into the build files as necessitated by certain code changes (e.g. the introduction of new modules). In some cases there hints to gazelle in the build files, such as `# gazelle:erlang...` or `# keep` comments. xref checks on plugins that depend on the cli are a good example.
2023-02-23 21:47:41 +08:00
"//deps/rabbit:erlang_app",
Use improved assert_suites2 macro from rules_erlang 3.9.0
2022-11-24 22:46:08 +08:00
"//deps/rabbit_common:erlang_app",
],
)
assert_suites()
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 improved assert_suites2 macro from rules_erlang 3.9.0
2022-11-24 22:46:08 +08:00
alias(
name = "amqp_client",
actual = ":erlang_app",
visibility = ["//visibility:public"],
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 generated bazel files Bazel build files are now maintained primarily with `bazel run gazelle`. This will analyze and merge changes into the build files as necessitated by certain code changes (e.g. the introduction of new modules). In some cases there hints to gazelle in the build files, such as `# gazelle:erlang...` or `# keep` comments. xref checks on plugins that depend on the cli are a good example.
2023-02-23 21:47:41 +08:00
eunit(
name = "eunit",
target = ":test_erlang_app",
)