ci(test): stop containers at the beginning of the run

An attempt to prevent updated container definitions clashing in CI GH
runners between different branches.

A self-hosted runner only runs a single job at a time.

If a container is already running there, an updated docker compose
file might fail to recreate that container, failing the run.
This commit is contained in:
Thales Macedo Garitezi 2022-10-10 09:19:50 -03:00
parent 373bd41170
commit e72e1567a1
2 changed files with 26 additions and 0 deletions

View File

@ -24,6 +24,11 @@ jobs:
steps:
- uses: actions/checkout@v1
# to avoid dirty self-hosted runners
- name: stop containers
run: |
docker rm -f $(docker ps -qa) || true
docker network rm $(docker network ls -q) || true
- name: docker compose up
env:
LDAP_TAG: ${{ matrix.ldap_tag }}
@ -79,6 +84,10 @@ jobs:
steps:
- uses: actions/checkout@v1
- name: stop containers
run: |
docker rm -f $(docker ps -qa) || true
docker network rm $(docker network ls -q) || true
- name: docker-compose up
run: |
docker-compose \
@ -150,6 +159,10 @@ jobs:
steps:
- uses: actions/checkout@v1
- name: stop containers
run: |
docker rm -f $(docker ps -qa) || true
docker network rm $(docker network ls -q) || true
- name: docker-compose up
timeout-minutes: 5
run: |
@ -236,6 +249,10 @@ jobs:
- tcp
steps:
- uses: actions/checkout@v1
- name: stop containers
run: |
docker rm -f $(docker ps -qa) || true
docker network rm $(docker network ls -q) || true
- name: docker-compose up
run: |
docker-compose \
@ -317,6 +334,10 @@ jobs:
steps:
- uses: actions/checkout@v1
- name: stop containers
run: |
docker rm -f $(docker ps -qa) || true
docker network rm $(docker network ls -q) || true
- name: docker-compose up
run: |
docker-compose \

View File

@ -42,6 +42,11 @@ jobs:
use-self-hosted: false
steps:
- uses: actions/checkout@v2
# to avoid dirty self-hosted runners
- name: stop containers
run: |
docker rm -f $(docker ps -qa) || true
docker network rm $(docker network ls -q) || true
- name: docker compose up
if: endsWith(github.repository, 'emqx')
env: