feat(install-deps): Utilise services Docker pour les tests

Le fichier install-deps.yml a été modifié pour utiliser des services Docker (Postgres, Redis) directement définis dans le workflow au lieu d'exécuter des commandes docker à l'intérieur. Cela simplifie la configuration et rend les tests plus propres. Les variables d'environnement ont été ajustées en conséquence.
This commit is contained in:
Serreau Jovann
2025-07-17 10:43:29 +02:00
parent 5a12cce8b4
commit 676234c5cd

View File

@@ -54,15 +54,24 @@ jobs:
test:
name: 📦 Install Dependencies
runs-on: self-hosted
services:
postgres:
image: postgres:16
env:
POSTGRES_DB: symfony_user
POSTGRES_USER: your_db_user
POSTGRES_PASSWORD: app_db_test
redis:
image: redis:7
needs: install
container:
image: registre.esy-web.dev/actions:latest
env:
APP_ENV: test
MESSENGER_TRANSPORT_DSN: redis://host.docker.internal:15433/messages
DATABASE_URL: postgres://your_db_user:app_db_test@host.docker.internal:15432/symfony_user?serverVersion=16&charset=utf8
VAULT_SERVER: http://host.docker.internal:15434
VAULT_TOKEN: myroot
MESSENGER_TRANSPORT_DSN: redis://redis:6374/messages
DATABASE_URL: postgres://your_db_user:app_db_test@postgres:5432/symfony_user?serverVersion=16&charset=utf8
steps:
- name: Checkout code
@@ -84,53 +93,6 @@ jobs:
else
echo "Warning: No package.json found. Skipping Bun install."
fi
- name: Prune previous Docker artifacts
run: |
docker rm -f vault-ci postgres-ci redis-ci || true
docker network rm ci-network || true
- name: Start services on Docker
run: |
docker network create ci-network
docker run -d --rm --network ci-network -p 15434:8200 --name vault-ci -e "VAULT_DEV_ROOT_TOKEN_ID=myroot" --cap-add=IPC_LOCK hashicorp/vault:latest vault server -dev
docker run -d --rm --network ci-network -p 15432:5432 --name postgres-ci -e "POSTGRES_DB=symfony_user" -e "POSTGRES_USER=your_db_user" -e "POSTGRES_PASSWORD=app_db_test" postgres:16
docker run -d --rm --network ci-network -p 15433:6379 --name redis-ci redis:latest
echo "Waiting for services to be ready..."
# --- Add PostgreSQL readiness check ---
echo "Checking PostgreSQL readiness..."
# Loop until PostgreSQL is ready to accept connections
# We use the internal container name (postgres-ci) and port (5432)
# The pg_isready command checks if the server is accepting connections
# -h: host, -p: port, -U: user, -d: database
# PGPASSWORD is used to provide the password non-interactively
DB_HOST="127.0.0.1"
DB_PORT="15432"
DB_USER="your_db_user"
DB_NAME="symfony_user"
DB_PASSWORD="app_db_test" # Use the actual password
# Install postgresql-client if pg_isready is not available in the runner image
# This is a common requirement for `pg_isready`
apt-get update && apt-get install -y postgresql-client || true # Install client tools, ignore if already installed
for i in $(seq 1 30); do # Try for up to 30 seconds (30 * 1 second sleep)
PGPASSWORD=$DB_PASSWORD pg_isready -h $DB_HOST -p $DB_PORT -U $DB_USER -d $DB_NAME
if [ $? -eq 0 ]; then
echo "PostgreSQL is ready!"
break
fi
echo "PostgreSQL not ready yet. Waiting..."
sleep 1
done
PGPASSWORD=$DB_PASSWORD pg_isready -h $DB_HOST -p $DB_PORT -U $DB_USER -d $DB_NAME
if [ $? -ne 0 ]; then
echo "PostgreSQL did not become ready in time. Exiting."
exit 1
fi
# --- End PostgreSQL readiness check ---
docker ps
- name: Setup PHP for testing
uses: shivammathur/setup-php@v2