|
| 1 | +# Buzz CI MinIO |
| 2 | + |
| 3 | +`ghcr.io/block/buzz-minio:latest` contains MinIO and `mc` for the disposable |
| 4 | +Linux AMD64 CI runners. `docker-compose.ci.yml` selects it for both services; |
| 5 | +development and deployment defaults stay in `docker-compose.yml`. |
| 6 | + |
| 7 | +The **MinIO image** workflow builds only when its inputs change, or on a manual |
| 8 | +dispatch. Pull requests build and smoke-test without publishing. On `main`, a |
| 9 | +successful smoke test publishes the same image as |
| 10 | +`sha-<full commit>-run-<run id>-<attempt>` and `latest`. The run-specific tag |
| 11 | +preserves each build, including package refreshes from the same source commit. |
| 12 | +Once consumers adopt the override, ordinary CI only pulls it; there is no build |
| 13 | +fallback or dependency on the publisher. `latest` deliberately floats, and |
| 14 | +Compose always pulls it. Docker's pull output records the resolved digest. |
| 15 | + |
| 16 | +The Dockerfile uses the same upstream releases as the development services, |
| 17 | +with checksummed official GitHub release binaries and a digest-pinned Alpine |
| 18 | +base. MinIO and `mc` are AGPL-3.0; their corresponding source is available at |
| 19 | +the [MinIO release](https://github.com/minio/minio/tree/RELEASE.2025-09-07T16-13-09Z) |
| 20 | +and [mc release](https://github.com/minio/mc/tree/RELEASE.2025-08-13T08-35-41Z). |
| 21 | + |
| 22 | +## First publication |
| 23 | + |
| 24 | +The image must exist and be publicly pullable before the CI switch can pass. |
| 25 | +Use two separate PRs: Buzz only permits squash merges, so two commits in one |
| 26 | +PR cannot stage this rollout. |
| 27 | + |
| 28 | +1. Merge the publisher-only PR containing `.github/ci/minio/`, |
| 29 | + `.github/workflows/minio-image.yml`, and the opt-in `docker-compose.ci.yml`. |
| 30 | + Ordinary CI does not select the override yet, so it does not need this image |
| 31 | + to validate the publisher PR. The merge triggers the first publication. |
| 32 | +2. After publication succeeds, an org/package admin must make **buzz-minio** |
| 33 | + public in its GitHub package settings (new GHCR packages default to private, |
| 34 | + even for public repositories). Verify an anonymous pull of |
| 35 | + `ghcr.io/block/buzz-minio:latest`. |
| 36 | +3. Rebase the separate consumer PR onto `main`, run its integration checks, and |
| 37 | + merge it. That PR selects the override in relay and mesh lifecycle CI. |
| 38 | + |
| 39 | +Subsequent publications preserve package visibility. |
| 40 | + |
| 41 | +## Updating or rebuilding |
| 42 | + |
| 43 | +Update the release URLs/checksums or base digest in the Dockerfile and open a |
| 44 | +PR. Merging triggers publication. To rebuild the existing recipe (for example, |
| 45 | +to pick up Alpine package updates), dispatch **MinIO image** from `main`. |
| 46 | +Manual dispatch disables Docker's layer cache so the package installation |
| 47 | +runs again. Other refs can build and test but cannot publish `latest`. |
| 48 | + |
| 49 | +To reproduce a CI run with a recorded version, set `MINIO_CI_IMAGE` to |
| 50 | +the published run-specific tag or digest while using |
| 51 | +`COMPOSE_FILE=docker-compose.yml:docker-compose.ci.yml`. |
0 commit comments