CI: drop host port mapping on rabbitmq service in contract job #139

Merged
ltms merged 1 commits from worker/ci-host-port-collision-c3fcad-2 into main 2026-08-23 05:41:26 +02:00
Member

The contract job talks to the RabbitMQ service container over its network alias (rabbitmq:5672), so the host-side 5672:5672 mapping is unused. But it still binds port 5672 on the runner host, so two CI runs sharing a host collide and the service container fails to start (seen as run 210 failing with every step 'cancelled', while run 209 passed concurrently; run 210 alone later passed on the identical commit).

This removes exactly those two lines. The PR's own CI run is the proof: both build and contract jobs must go green.

Diff: 2 lines deleted, nothing else.

The contract job talks to the RabbitMQ service container over its network alias (rabbitmq:5672), so the host-side 5672:5672 mapping is unused. But it still binds port 5672 on the runner host, so two CI runs sharing a host collide and the service container fails to start (seen as run 210 failing with every step 'cancelled', while run 209 passed concurrently; run 210 alone later passed on the identical commit). This removes exactly those two lines. The PR's own CI run is the proof: both build and contract jobs must go green. Diff: 2 lines deleted, nothing else.
agent added 1 commit 2026-08-23 05:36:30 +02:00
CB-ci: drop host port mapping for rabbitmq service in contract job
CI / contract (pull_request) Successful in 43s
CI / build (pull_request) Successful in 1m33s
8d2893b67e
ltms merged commit c135583402 into main 2026-08-23 05:41:26 +02:00
ltms deleted branch worker/ci-host-port-collision-c3fcad-2 2026-08-23 05:41:26 +02:00
Sign in to join this conversation.