mirror of
https://github.com/hanzoai/s3-csi.git
synced 2026-11-03 03:09:20 +00:00
4ea323487b
This repo had seven GitHub workflows. Three of them -- dev.yaml, release.yaml and versioned_release.yaml -- built THE SAME two images, ghcr.io/hanzoai/s3-csi and ghcr.io/hanzoai/s3-mount. Three builders on one commit is three chances to publish something nobody asked for, and no single place that says what this repo produces. Now there is one: the repo-root hanzo.yml, which platform.hanzo.ai reads and the hanzoai/ci reusable gates from, exactly as hanzoai/cloud does it. .github/workflows is gone entirely. The pipelines that carry their own weight -- the kind integration suite and the two helm chart jobs -- moved to .hanzo/workflows unchanged; they keep runs-on: ubuntu-latest because our git-runner registers that label itself (ubuntu-latest:docker://catthehacker/ubuntu:act-24.04), so the same line now means our runner instead of GitHub's. prepare_release.yaml is dropped: bumping a dependency and cutting a tag is the platform's job, not a workflow's. Co-authored-by: hanzo-dev <[email protected]>
19 lines
541 B
YAML
19 lines
541 B
YAML
name: CI/CD
|
|
# The ONE pipeline for s3-csi, on our own runners against git.hanzo.ai.
|
|
#
|
|
# THE LAW: this repo has no .github/workflows. Everything that gates, builds or
|
|
# deploys lives here, and every real detail lives in the repo-root hanzo.yml so
|
|
# platform.hanzo.ai reads the same declaration this pipeline does.
|
|
on:
|
|
push:
|
|
branches: [main]
|
|
pull_request:
|
|
workflow_dispatch:
|
|
concurrency:
|
|
group: cicd-${{ github.ref }}
|
|
cancel-in-progress: true
|
|
jobs:
|
|
gate:
|
|
uses: hanzoai/ci/.hanzo/workflows/build.yml@v2
|
|
secrets: inherit
|