cdbaf4b475
The deploy step did 'kubectl set image deployment/tidaldb' on every image build, coupling image builds to a standalone roll. Deployment is manual via kustomize from the orchard9-k3sf ops repo (its contract: no CI/CD deploy). The one tidal-server binary serves both standalone and multi-process 'cluster --region' modes, so this image covers the m8p10 3/3 cluster deploy too. Adds an explicit 'm8p10' image tag for deterministic manifest pinning.
27 lines
948 B
YAML
27 lines
948 B
YAML
# Build-only pipeline: Kaniko builds the tidal-server image and pushes it to the
|
|
# in-cluster zot registry. DEPLOYMENT IS MANUAL (kustomize, from the orchard9-k3sf
|
|
# ops repo) — the old auto-`kubectl set image deployment/tidaldb` step was removed
|
|
# because it coupled every image build to a standalone roll and the cluster ops
|
|
# repo's contract is "manual deploy via scripts, no CI/CD deploy". The same
|
|
# `tidal-server` binary serves every subcommand (standalone AND multi-process
|
|
# `cluster --region`), so one image covers both deployments.
|
|
when:
|
|
branch: main
|
|
event: push
|
|
|
|
steps:
|
|
build:
|
|
image: woodpeckerci/plugin-kaniko
|
|
settings:
|
|
repo: tidal/server
|
|
dockerfile: docker/standalone/Dockerfile
|
|
context: .
|
|
tags:
|
|
- latest
|
|
- m8p10
|
|
- ${CI_COMMIT_SHA}
|
|
registry: registry.threesix.ai
|
|
build_args:
|
|
- TARGETPLATFORM=linux/amd64
|
|
extra_args: --customPlatform=linux/amd64
|