eblume/blumeops
1
1
Fork 0
Code Issues Pull requests Projects Releases 83 Packages Wiki Activity Actions
blumeops/docs/how-to/forgejo-runner/validate-workflows-against-v12.md
Erich Blume c86b5d7772
All checks were successful
Build Container / detect (push) Successful in 3s
Details
Build Container / build-dagger (navidrome) (push) Successful in 22m26s
Details
Native Dagger container builds + Navidrome v0.61.1 (#330) 
## Summary
- Move Dagger module from `.dagger/` to repo root (`src/blumeops/`), rename `blumeops-ci` → `blumeops`
- Replace opaque `docker_build()` with native Dagger pipelines that surface full build errors per step
- Migrate navidrome as the first container (`containers/navidrome/container.py`)
- Upgrade navidrome from v0.60.3 to v0.61.1 (major artwork overhaul, SQLite FTS5 search, server-managed transcoding)
- Add `dagger call container-version` for CI version extraction without Dockerfile parsing
- All mise tasks (`container-list`, `container-version-check`, `container-build-and-release`) updated for hybrid mode
- Legacy `docker_build()` fallback preserved for all other containers

## Motivation
When navidrome v0.61.0 added a new Go build tag (`sqlite_fts5`), `docker_build()` showed only "exit code: 1". We had to run `docker build --progress=plain` manually to find `undefined: buildtags.SQLITE_FTS5`. Native Dagger pipelines show the full error inline.

## Container build dispatch needed
After merge, dispatch container build for navidrome:
```
mise run container-build-and-release navidrome --ref 470b4bd
```

## Deploy steps
1. Wait for container build to complete
2. Back up navidrome-data PVC (non-reversible DB migrations)
3. `argocd app set navidrome --revision main && argocd app sync navidrome`
4. Verify at https://dj.ops.eblu.me

## Future
Remaining containers migrate incrementally in follow-up PRs using the same pattern.

Reviewed-on: #330
2026-04-11 17:11:56 -07:00

1.2 KiB
Raw Blame History

title modified last-reviewed tags
Validate Workflows Against v12 2026-04-11 2026-02-27
how-to
forgejo-runner
ci

Validate Workflows Against v12

Run forgejo-runner validate (available from v9.0+) against all workflow files to catch schema issues before upgrading the k8s runner daemon.

Result

All 6 workflows pass v12.7.0 schema validation with no changes needed:

  • branch-cleanup.yaml — OK
  • build-blumeops.yaml — OK
  • build-container-nix.yaml — OK
  • build-container.yaml — OK
  • cv-deploy.yaml — OK
  • deploy-fly.yaml — OK

Deliverables

  1. validate_workflows function added to src/blumeops/main.py (formerly .dagger/src/blumeops_ci/main.py)
    • Uses forgejo-runner validate --directory . inside the upstream runner container
    • runner_version parameter (default 12.7.0) pins to deployed version
  2. mise run validate-workflows task wired to dagger call validate-workflows
  3. Pre-commit hook triggers on .forgejo/workflows/ changes

Usage

mise run validate-workflows
# or directly:
dagger call validate-workflows --src=.

Related