j.r/distributed-execution
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

[SIMPL-30451] Drop the Gitea workflow from the GitLab repository

Browse Source 
This repository is built by the shared ds.gitlab-ci.yml template; carrying a second CI system alongside it invited the reader to wonder which one is authoritative. The Gitea Actions workflow that builds both images stays in the sandbox Gitea mirror, which is where the sandbox images are produced.

The README, the pipes payload values and the sandbox values no longer point at a file this repository does not contain.

Changelog: removed
This commit is contained in:
ILay
2026-08-31 17:26:08 +02:00
parent b625b64df2
commit 899429b10a
4 changed files with 7 additions and 159 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
yaml/loosely-coupled/values-pipes-payload.yaml
View File

@@ -17,8 +17,7 @@
# For values that work today, see yaml/sandbox/values-sandbox-gitea.yaml. The
# shared GitLab pipeline (ds.gitlab-ci.yml) builds exactly one image per project -
# $CI_REGISTRY_IMAGE from the root Dockerfile - so the payload reference below
# resolves only once that pipeline learns to build a second image. The Gitea
# workflow in .gitea/workflows/docker-publish.yml already builds both.
# resolves only once that pipeline learns to build a second image.
dagster:
dagster-user-deployments: