Skip to content

GitLab Status: recognize and retry builder runner failures - #13

Merged
ruscher merged 2 commits into
biglinux:mainfrom
ruscher:main
Oct 12, 2026
Merged

ruscher merged 2 commits into
biglinux:mainfrom
ruscher:main

Conversation

@ruscher

@ruscher ruscher commented Oct 12, 2026

Copy link
Copy Markdown
Member

The testing-2026-10-11 request reached the builder (pipeline 37669), but the builder's runner failed with runner_system_failure (Kubernetes 502) before building. GitLab Status now recognizes that within seconds, re-runs the build job of the Build Package run (at most twice) and follows the new request. Tested in ruscher#6.

The testing-2026-10-11 request reached the builder 1 s after the run
(pipeline 37669), but its first job died with runner_system_failure
(Kubernetes 502 Bad Gateway) before any build job existed. The tracker
only looked for build jobs, so it waited 10 min and reported that no job
started.

- track-build.sh: a failed request pipeline for the package right after
  the request, or a build job that failed for a runner reason, ends with
  exit status 3 and the GitLab job link.
- gitlab-status.yml: on status 3, re-run the "build" job of that Build
  Package run (at most twice, only from the tracker of attempt 1) and
  follow the new request. The organization webhook fires for re-runs too
  (pipeline 37694, 2 s after the manual re-run).
GitLab Status: recognize and retry builder runner failures
@ruscher
ruscher merged commit a72068e into biglinux:main Oct 12, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant