2909 — Deploy from gitlab.epfl.ch¶
Why¶
On 2026-09-22 GitHub stopped running Actions for the whole EPFL-ENAC org,
public repos included. The Argo repos' update_manifest workflow stopped
too, so a repository_dispatch would be accepted and deploy nothing.
Billing was fixed the same day. dev stays on GitLab anyway, so the
fallback keeps running for real instead of rotting until the next outage.
What shipped¶
.gitlab-ci.ymlincludes the componentgitlab.epfl.ch/EPFL-ENAC/build-push-deploy/deploy@0.3.0with the same inputs asdeploy.yml: three build contexts, the chart smoke renders,GIT_SHAandAPP_VERSION.scripts/app-version.shcomputesAPP_VERSIONfor both pipelines, readingGITHUB_*orCI_*. One copy, so the two cannot drift.mirror-to-gitlab.ymlpushes everydevchange to GitLab (deploy keyGITLAB_DEPLOY_KEY, pinned host key). GitLab CE cannot pull from GitHub, and a push nobody remembers is a silent fallback. Since 2026-09-23 it is a 20-line caller of the reusable workflow in the action (v3.10.0).- Image reuse (
reuse_unchanged_images,build_key_paths: package.json, no per-deploy rescan), sameenac.build.keyformula and label asdeploy.yml, so both paths recognise each other's images. Component0.3.0, 2026-09-23. - One pipeline per ref. GitLab runs on
devonly.deploy.ymldropsdevand keepsstage,ci-test/**andv*.*.*. Two pipelines on the same ref would each commit a different digest to the same overlay. - The component replaces
epfl-enac-build-push-deploy-action: - build, push to ghcr, Trivy HIGH/CRITICAL,
crane copyto quay (same digest) - chart
1.0.<CI_PIPELINE_ID>[-dev|-rc]; pipeline ids are instance-wide and already above the GitHub run numbers, so versions keep increasing - overlay commits through GitHub's
createCommitOnBranch, instead of a dispatch - skips an image or chart the overlay doesn't list, and fails if none of the images is in it
- Runners: the group VM runner (#4562) and
enack8s(#5224), EPFL-ENAC/enack8s-app-config#361 and #362. Both are privileged fordocker:dind.enack8stakes protected refs only. - Variables: group
GHCR_USERNAME,GHCR_TOKENandMANIFEST_TOKEN; projectQUAY_USERNAMEandQUAY_PASSWORD(svc1751+ghaction).
Verified¶
- Pipeline 426358 on
ci-test/gitlab-deploy: all three images built on both runners, Trivy clean, same digests on ghcr and quay, chart1.0.426358-devpushed. - Overlay edits dry-run against the real dev overlays of both Argo repos:
only digests and the chart version change.
docsis skipped on enack8s, which doesn't deploy it. -
The manifest job's real script ran in Alpine against a stubbed GitHub API and produced one correct commit request per Argo repo.
-
First real
devdeploy, 2026-09-22: #2911 merged → mirror run green from GitHub's runners (gitlab.epfl.ch is reachable from the public internet) → GitLab pipeline 426465 green → overlay commits enack8s-app-config91a66806and openshift-app-config19bcae08through the shared script, chart1.0.426465-dev.
Operating it¶
GitHub stays where PRs merge. mirror-to-gitlab.yml pushes dev to
gitlab.epfl.ch, which deploys it. If GitHub Actions is down, push by hand:
git fetch origin && git push gitlab origin/dev:dev
Chart versions on GitLab are 1.0.<pipeline id>-dev (~426k), far above
GitHub's run numbers. Harmless while dev stays on GitLab; if it ever
moves back, GitHub's chart-reuse check would see the GitLab version as
"latest" and republish once per run.
- Reuse, 2026-09-23: pipeline 426659 rebuilt everything once (no labels yet); pipeline 426661 on the same commit reused all three images and the chart (build jobs 20–29 s) and left both overlays untouched.
Stage and release tags (2026-11-18)¶
quay-its.epfl.ch stopped accepting traffic from outside the EPFL network.
GitHub-hosted runners then failed to deploy: the stage run and tag
v1.4.22 stopped at Get "https://quay-its.epfl.ch/v2/": EOF. The
gitlab.epfl.ch runners are inside EPFL and still reach quay.
.gitlab-ci.ymlruns ondev,stageand tagsvX.Y.Z(exact SemVer, no pre-release). Component0.4.0: a SemVer tag publishes chartX.Y.Zwith appVersion set to the tag, and only a SemVer tag updates the prod overlay.deploy.ymlis deleted.ci-test/**no longer deploys.mirror-to-gitlab.yml(v4.2.0) pushesdev,stageandv*.*.*tags. It pushes a tag as a tag.- GitHub keeps the code, the PRs and "Tag and Release". The tag that workflow creates with its PAT triggers the mirror.
GitLab setup: protect stage and the v* tags, and let the deploy key
push to them. Protected variables and the enack8s runner only serve
protected refs.
Not ported¶
The action's private_key, lfs and submodules inputs; co2 uses none of
them. Tracking: https://gitlab.epfl.ch/EPFL-ENAC/build-push-deploy/-/work_items/1.