deploy steam: steamcmd "Failed to commit build : Failure" (exit 6) is a false negative - build was uploaded and registered

Abierto
  • ¿Algo no está bien?
#310 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
52/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
typescript
Área
cli

Línea de trabajo

Start with parse-steamcmd-output.ts and trace how its success checks feed the Steam deployment command. Reproduce or examine the reported output where content uploads and registers despite the commit error, then determine how that case should be distinguished from a real failure. Done means tests cover the reported output and a genuine failure, without treating an unconfirmed upload as successful.

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

Descripción

Observed behavior

game-ci deploy steam (v0.1.75) intermittently fails with:

[ERROR] Error: Steam deployment failed: exit code 6: . 72.9MB (94%) | . | [timestamp]: ERROR! Failed to commit build for AppID 3570680 : Failure | Unloading Steam API...OK |

...while the build was uploaded and registered successfully: it appears in the Steamworks build manager, and a manually set-live build from this run is serving on the default branch. The same workflow/CLI was fully green on a release a few weeks earlier (Successfully finished), with the steam-deploy plugin code byte-identical between v0.1.72 and v0.1.75 (git diff v0.1.72...v0.1.75 touches no steam files), so this is a steamcmd-side reporting race, not a code regression.

A second attempt minutes later re-uploaded instantly (chunk dedup) and failed at the commit step the same way, yet that build also registered.

Impact

parse-steamcmd-output.ts requires /Successfully finished/ or exit 0, so this benign-but-reported failure aborts multi-app deploy jobs (we lost the demo and playtest deploys because they run after the full deploy in the same job), and blind retries create duplicate builds in the build manager.

Suggestion

When steamcmd reports the commit failure after depot content uploaded successfully, surface a warning instead of a hard error - or optionally poll the build status (e.g. via the partner web API) to confirm registration before failing. As-is, operators must choose between silent duplicates and missed downstream deploys.

Lenguaje dominante
TypeScript
Estrellas
20
Forks
11
Merge medio
5 h 28 min
PR fusionados (30 d)
4

Preparar el entorno

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 game-ci/cli

Todos los issues de game-ci/cli

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.