Tested versions¶
These are the versions on main. A release pins whatever main held when it was cut.
The broker¶
| Image | apache/artemis:2.57.0-alpine |
| Pinned in | the image constant in test/integration/main_test.go |
| Configuration | test/integration/testdata/broker.xml, mounted as the image's etc-override/broker.xml |
| Run by | testcontainers-go v0.44.0 and its artemis module v0.44.0, under INT_TEST_INTEGRATION=1 |
That is the only broker version the suite has run against, and Artemis the only broker. The suite has not been run against any other AMQP 1.0 broker.
The fixture's broker.xml is the image's own, with the delivery-count and journal settings on, the
disk-usage limit off, and address settings for the suite's subjects. The settings that matter to the
adapter:
| Setting | Value | Why |
|---|---|---|
persistence-enabled |
true |
part of Persists. |
persist-delivery-count-before-delivery |
true |
PersistsDeliveryCount, which SurvivesRestart needs. |
journal-sync-non-transactional |
true |
part of Persists. |
max-disk-usage |
-1 |
the disk limit is off. |
address settings for a.#, b.# |
dead-letter address DLQ, max-delivery-attempts 10, auto-create on, auto-delete of queues on |
the suite's subjects. |
address settings for c.# |
dead-letter address NoQueueDLA, which has no queue |
proves the refusal for a dead-letter address with no queue. |
the amq role |
all permissions, manage included |
the adapter uses the management address. |
The Artemis management code carries a comment that it needs Artemis 2.44.0 or later. The fixture
pinned apache/activemq-artemis:2.44.0-alpine until the image moved, and now runs 2.57.0.
Nothing between or below those has been run, and 2.44.0 itself is no longer run.
The open pin ticket¶
The fixture's Artemis image was renamed upstream, so its pin can't be bumped
is open. The upstream repository stopped at 2.44.0 on Docker Hub and Artemis now publishes as
apache/artemis. The fixture moved to the new name and to 2.57.0 in
merge request 44. What is
left is that no automatic updater tracks the pin: the estate presets' managers read only
.gitlab-ci.yml, and a Go constant is not one of them, so the version will not advance by itself. The
ticket is blocked on that
(cicd#93). Treat 2.57.0 as the version tested,
not the newest.
Go modules¶
From go.mod:
| Module | Version |
|---|---|
gitlab.com/phpboyscout/go/messaging |
v0.9.0 |
github.com/Azure/go-amqp |
v1.7.0 |
gitlab.com/phpboyscout/go/envelope |
v0.1.0 |
gitlab.com/phpboyscout/go/envelope-cloudevents |
v0.1.0 |
gitlab.com/phpboyscout/go/envelope-masstransit |
v0.1.0 |
gitlab.com/phpboyscout/go/envelope-nservicebus |
v0.1.0 |
gitlab.com/phpboyscout/go/errors |
v0.3.0 |
The module is go 1.27.3.
What the suite is, and runs where¶
The conformance suite runs in CI's Docker-in-Docker integration job (enable_integration, a 25 minute
timeout, ./test/integration/...). It includes a container restart, which is why the timeout is
long. See Run the conformance suite.