From 835eb51eafc0a16f462938e529eef601c8719c17 Mon Sep 17 00:00:00 2001 From: AlexeerCT Date: Fri, 24 Apr 2026 14:10:30 -0500 Subject: [PATCH] Refactor Alembic command in Jenkinsfile for clarity and correctness - Updated the Alembic upgrade command to use the `--config` option instead of `-c`, addressing ambiguity in configuration handling. - Revised comments to enhance understanding of the command's context and implications during E2E testing. --- Jenkinsfile | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Jenkinsfile b/Jenkinsfile index 99181fa7..1fa5a442 100644 --- a/Jenkinsfile +++ b/Jenkinsfile @@ -284,8 +284,8 @@ pipeline { e2e_compose_fail_logs exit 1 fi - # Sin sh -c ni .sh bajo /app: sin comillas frágiles y sin depender de un fichero no montado aún (push) - if ! e2e_compose run --rm --no-deps --entrypoint python3 backend -m alembic -c /app/alembic.ini upgrade head; then + # Nunca usar "python3 -m alembic -c": el -c es ambigüo; Alembic recibe un config vacío (No 'script_location') + if ! e2e_compose run --rm --no-deps --entrypoint python3 backend -m alembic --config /app/alembic.ini upgrade head; then echo "ERROR: falló alembic upgrade head (job previo al stack completo)" e2e_compose_fail_logs exit 1