Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

[CI failure] Production deployment migration step runs without repository checkout

Cerrado Apto para principiantes
  • ¿Algo no está bien?
#1,466 2 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
1/5
Tiempo estimado
Menos de una hora
Aptitud para principiantes
78/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
bash, github-actions, yaml
Área
ci-cd

Línea de trabajo

Lee .github/workflows/Build-Test-And-Deploy.yml y compara los pasos de checkout de deploy-development con la invocación del script en deploy-production. Confirma en el registro de la ejecución 37543212282 qué paso falló; luego añade checkout al trabajo de producción antes de que ejecute scripts/run-ef-migration-job.sh y vuelve a ejecutar el workflow; estará listo cuando el paso de migración encuentre el script y la implementación continúe correctamente después de ese paso.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

bug

Summary

The post-merge deployment run is most likely failing in deploy-production at the new Run database migrations step because that job invokes scripts/run-ef-migration-job.sh without first checking out the repository. GitHub Actions jobs start without workspace source files; therefore Bash cannot find the script. The same commit adds actions/[email protected] to deploy-development, but not to deploy-production.

Failure details

  • Run: https://github.com/IntelliTect/EssentialCSharp.Web/actions/runs/37543212282
  • Commit: 8909cde2042ba857bf6e5eb5f72eb6f2140633be
  • Failed job and step: Likely deploy-production / Run database migrations (the raw run-log endpoint is not exposed by the available GitHub read interface)
  • Classification: Workflow or environment configuration
  • Confidence: High for the workflow defect; medium for attributing this specific run to that defect until the failed-step log is checked

Evidence

The commit diff for .github/workflows/Build-Test-And-Deploy.yml adds checkout at approximately lines 287-288 inside deploy-development. It adds the production migration step at approximately lines 391-398:

- name: Run database migrations
  env:
    MIGRATION_IMAGE: ${{ vars.PRODCONTAINER_REGISTRY }}/essentialcsharpweb@${{ steps.import.outputs.digest }}
    MIGRATION_JOB_NAME: ${{ vars.MIGRATION_JOB_NAME }}
    RESOURCEGROUP: ${{ vars.RESOURCEGROUP }}
  run: bash scripts/run-ef-migration-job.sh

No corresponding checkout is added to deploy-production. The script exists only in the repository at scripts/run-ef-migration-job.sh, so the expected confirmation is a production-job error such as bash: scripts/run-ef-migration-job.sh: No such file or directory. The script itself was introduced by the same commit. The existing PR review identified related deployment-job wiring risks, and no open issue was found for this exact checkout omission.

Recommended actions

  • Add - uses: actions/[email protected] as the first step in deploy-production, before the migration step, then rerun the workflow.
  • Confirm run 37543212282's failed-step log contains the missing-script error; if it instead fails inside Azure CLI, retain this checkout fix and open a separate issue for the Azure error rather than conflating the causes.
  • Add a workflow validation or smoke check that verifies every job executing a repository script has an explicit checkout step.

Prevention

Keep repository-script execution behind an explicit checkout in every job, and add a static workflow check that flags run: bash scripts/ in jobs lacking actions/checkout.

Generated by CI Failure Doctor · copilot · gpt56 · 10.4 AIC · ⌖ 2.61 AIC · ⊞ 24K · ◷

Add this agentic workflow to your repo

To install this agentic workflow, run

gh aw add githubnext/agentics/workflows/ci-doctor.md@5d11aa2a05ce2c943c085acb7b12b583f83ed375
Lenguaje dominante
HTML
Estrellas
8
Forks
8
Merge medio
1 d 7 h
PR fusionados (30 d)
90

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de IntelliTect/EssentialCSharp.Web

Todos los issues de IntelliTect/EssentialCSharp.Web

Issues similares

Más issues de DevOps

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.