ci(deploy): auto-deploy the GUI via the self-hosted runner#54
Merged
Conversation
Mirror image of the backend (obcode/glabs) deploy job: a gated `deploy` job on the shared self-hosted runner (label glabs-deploy) that, on a release, pins GUI_TAG in the on-host .env and rolls only the `gui` service. The docker-compose.yml lives in and is synced by the glabs repo; here we only pull + up -d gui. Gated by `if: vars.AUTO_DEPLOY == 'true'` — until the GUI runner exists and the variable is set, the image is still built & pushed and this job is skipped. See obcode/glabs deploy/README.md "Automatischer Deploy". Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Der glabs.gui-Teil des Auto-Deploys (Backend-Teil: obcode/glabs #130). Spiegelbildlich zum Backend-Deploy-Job.
Inhalt
docker.yml— neuer, gateddeploy-Job (needs: build-and-push-image,if: vars.AUTO_DEPLOY == 'true',runs-on: [self-hosted, glabs-deploy]— gleiches Label/Runner wie Backend): pinntGUI_TAGin der on-host.envund rollt nur dengui-Service (docker compose pull gui+up -d gui+ prune). Diedocker-compose.ymlselbst liegt im glabs-Repo und wird von dessen Deploy-Job gesynct.VERSIONausgithub.event.release.tag_name || inputs.tag(beide Trigger, mit v-Präfix wie die Registry-Historie).Verifikation
actionlint: nur die erwartete Info „unbekanntes self-hosted-Labelglabs-deploy" (Custom-Label) — kein Fehler.inputs.tagexistiert imworkflow_dispatchoben → im Deploy-Job gültig.AUTO_DEPLOY=true(per Design).ci:-Titel → kein Release-Bump.🤖 Generated with Claude Code