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

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

129 lines
2.6 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")
Add rabbitmq_trust_store to bazel
2021-05-07 19:01:01 +08:00
load("//:rabbitmq_home.bzl", "rabbitmq_home")
load("//:rabbitmq_run.bzl", "rabbitmq_run")
load(
"//:rabbitmq.bzl",
Add dialyze for remaning tier-1 plugins
2021-06-01 16:19:10 +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",
Futher bazel file refactoring and deduplication
2021-05-11 22:15:16 +08:00
"rabbitmq_integration_suite",
Add rabbitmq_trust_store to bazel
2021-05-07 19:01:01 +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 rabbitmq_trust_store to bazel
2021-05-07 19:01:01 +08:00
APP_NAME = "rabbitmq_trust_store"
APP_DESCRIPTION = "Client X.509 certificates trust store"
APP_MODULE = "rabbit_trust_store_app"
APP_ENV = """[
{default_refresh_interval, 30},
{providers, [rabbit_trust_store_file_provider]}
]"""
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")
Add rabbitmq_trust_store to bazel
2021-05-07 19:01:01 +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_srcs(name = "all_srcs")
Add rabbitmq_trust_store to bazel
2021-05-07 19:01:01 +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
test_suite_beam_files(name = "test_suite_beam_files")
# gazelle:erlang_app_extra_app ssl
# gazelle:erlang_app_extra_app crypto
# gazelle:erlang_app_extra_app public_key
# gazelle:erlang_app_extra_app inets
Add rabbitmq_trust_store to bazel
2021-05-07 19:01:01 +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 rabbitmq_trust_store to bazel
2021-05-07 19:01:01 +08:00
app_description = APP_DESCRIPTION,
app_env = APP_ENV,
app_module = APP_MODULE,
app_name = APP_NAME,
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 = [
"crypto",
"public_key",
"ssl",
"inets",
],
license_files = [":license_files"],
priv = [":priv"],
deps = [
"//deps/rabbit:erlang_app",
"//deps/rabbit_common:erlang_app",
],
Add rabbitmq_trust_store to bazel
2021-05-07 19:01:01 +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",
)
Add xref for remaining tier-1 plugins
2021-05-25 17:39:03 +08:00
Add dialyze for remaning tier-1 plugins
2021-06-01 16:19:10 +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 remaning tier-1 plugins
2021-06-01 16:19:10 +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",
Add dialyze for remaning tier-1 plugins
2021-06-01 16:19:10 +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",
)
eunit(
name = "eunit",
target = ":test_erlang_app",
Add dialyze for remaning tier-1 plugins
2021-06-01 16:19:10 +08:00
)
Add rabbitmq_trust_store to bazel
2021-05-07 19:01:01 +08:00
rabbitmq_home(
name = "broker-for-tests-home",
Mark additional rules as testonly
2023-03-01 04:29:33 +08:00
testonly = True,
Add rabbitmq_trust_store to bazel
2021-05-07 19:01:01 +08:00
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",
":erlang_app",
"//deps/amqp_client:erlang_app",
"@ct_helper//:erlang_app",
Add rabbitmq_trust_store to bazel
2021-05-07 19:01:01 +08:00
],
)
rabbitmq_run(
name = "rabbitmq-for-tests-run",
Mark additional rules as testonly
2023-03-01 04:29:33 +08:00
testonly = True,
Add rabbitmq_trust_store to bazel
2021-05-07 19:01:01 +08:00
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 = "config_schema_SUITE",
)
rabbitmq_integration_suite(
name = "system_SUITE",
flaky = True,
runtime_deps = [
"//deps/trust_store_http:erlang_app",
"@ct_helper//:erlang_app",
],
)
assert_suites()
Add rabbitmq_trust_store to bazel
2021-05-07 19:01:01 +08:00
Use improved assert_suites2 macro from rules_erlang 3.9.0
2022-11-24 22:46:08 +08:00
alias(
name = "rabbitmq_trust_store",
actual = ":erlang_app",
visibility = ["//visibility:public"],
Add rabbitmq_trust_store to bazel
2021-05-07 19:01:01 +08:00
)