These changes are generated by 'make actions-workflows'. The change to
the template that causes the diff is in the parent commit - adding a
suffixed of "-mixed" to the job names.
Without the suffix it's hard to tell apart regular and mixed version
workflows by name. Currently you need to go into the "Set up job" step
or look at the bazelisk cquery. Changing the names should have no
functional change - it's just easier to tell the jobs apart in the
GitHub UI.
This commit only updates the template. The child commit will regenerate
the workflow file via 'make actions-workflows'.
This appears to be an oversight when creating the mixed version
template: the CLI should use the mixed version workflow template rather
than the regular plugin workflow.
which fixes and issue with escript_archive that was breaking the rabbitmqctl escript
(cherry picked from commit 5fc8a8cb9a)
(cherry picked from commit 0ce73ff467)
It's technically a build target, so we didn't need to create a whole
new test rule, but it's marked as "manual" so that it doesn't cause
bazel build //... to fail
(cherry picked from commit f2add661f4)
(cherry picked from commit 7e8c9590b9)
I'm not actually sure why the changes to rabbitmqctl compilation
necessitated this change, but it seems to be the case
(cherry picked from commit 662ad8edf4)
(cherry picked from commit 2287a84889)
Certain elixir-native deps are still build with mix, but this can be
corrected later
(cherry picked from commit 5debebfaf3)
# Conflicts:
# deps/rabbit/BUILD.bazel
(cherry picked from commit 7f585d4102)
# Conflicts:
# deps/rabbitmq_cli/BUILD.bazel
# deps/rabbitmq_ct_helpers/BUILD.bazel
* Turn off BuildBuddy integration (#11343)
Builds now execute on the github actions workers, using Google Cloud Storage (GCS) as a cache
(cherry picked from commit a6874e39cc)
# Conflicts:
# .github/workflows/update-elixir-patches.yaml
# .github/workflows/update-otp-patches.yaml
# MODULE.bazel
# WORKSPACE
# deps/rabbitmq_peer_discovery_consul/test/system_SUITE_data/consul.hcl
(cherry picked from commit 2c62185317)
# Conflicts:
# .bazelrc
# .github/workflows/rabbitmq_peer_discovery_aws.yaml
# .github/workflows/templates/test-mixed-versions.template.yaml
# .github/workflows/templates/test.template.yaml
# .github/workflows/test-mixed-versions.yaml
# .github/workflows/test.yaml
# MODULE.bazel
# bazel/platforms/BUILD.bazel
* fixup backport
(cherry picked from commit dd62ac16f3)
# Conflicts:
# .github/workflows/update-elixir-patches.yaml
# .github/workflows/update-otp-patches.yaml
* remove rabbitmq_amqp_client tests from this branch
as the plugin does not exist here
(cherry picked from commit 28ee2ddee6)
# Conflicts:
# .github/workflows/test-mixed-versions.yaml
* Reduce bazel sandbox for rabbitmq_amqp1_0 tests in CI
since they use java
(cherry picked from commit 0d5c0e5086)
* Install daemonize as needed in the peer_discovery_etcd suite
(cherry picked from commit 23f6e5cc7e)
* fixup backport
* oauth2_client does not exist on this branch
and rabbitmq_prelaunch will run as part of the rabbit shards
* Use erlang 25.0/elixir 1.14 for mixed version tests
---------
Co-authored-by: Rin Kuryloski <rin.kuryloski@broadcom.com>
rabbitmq-diagnostics status: adjust the (date-based) support status field to match the current community support policy (backport #11386) (backport #11387)
Accidentally left out of #11343
(cherry picked from commit bdd18ed800)
# Conflicts:
# .github/workflows/templates/test-mixed-versions.template.yaml
# .github/workflows/templates/test.template.yaml
# .github/workflows/test-mixed-versions.yaml
# .github/workflows/test.yaml
(cherry picked from commit 57dba90b3d)
In certain shutdown scenarios this function on
Erlang 26 runs into exceptions that stem from
application_controller.
The objective of this function is to be
an exception-safe version of
application:which_applications/1, so let's
handle more cases.
This helps certain test suites avoid exceptions
(process crash reports) logged during shutdown,
which makes CT helpers fail test run even
though there were no exceptions in RabbitMQ
itself, and all the exception indicates is a
certain edge case (during system shutdown)
that application_controller does not care to handle.
(cherry picked from commit ca094402a9)
(cherry picked from commit addc990ac3)
remove fail_if_no_peer_cert as it is no longer accepted in Erlang 26 and will stop the connection from happening
(cherry picked from commit 23794e1115)
(cherry picked from commit 54c24b4809)
Michael Klishin
Diana Parra Corbacho
Michael Davis
Michael Klishin
Rin Kuryloski
GitHub
mergify[bot]
Michael Klishin
womblep