Commit Graph

20 Commits

Author SHA1 Message Date
98c3ef284f fix(ci): simplify workflow to matrix strategy for Gitea compat
Some checks failed
Build and Push Images / determine-version (push) Successful in 5s
Build and Push Images / build (Dockerfile.ray-worker-nvidia, nvidia) (push) Failing after 23m46s
Build and Push Images / build (Dockerfile.ray-worker-intel, intel) (push) Failing after 23m50s
Build and Push Images / build (Dockerfile.ray-worker-strixhalo, strixhalo) (push) Failing after 31s
Build and Push Images / build (Dockerfile.ray-worker-rdna2, rdna2) (push) Failing after 43s
Build and Push Images / Release (push) Has been skipped
Build and Push Images / Notify (push) Successful in 2s
- Replace 4 separate build jobs with single matrix build job
- Eliminates complex dependency graph causing 'must contain one job
  without dependencies' parse error in Gitea act_runner
- All if: conditions now use single-line strings (no multi-line |)
- workflow_dispatch image filter moved to step-level check
- Add stale buildx builder cleanup step before each build
- Simplify release/notify to depend on single 'build' job
2026-02-06 15:41:19 -05:00
3bc0b848de fix(ci): add amdsmi-shim to paths filter
Some checks failed
Build and Push Images / determine-version (push) Has been cancelled
Build and Push Images / build-nvidia (push) Has been cancelled
Build and Push Images / build-rdna2 (push) Has been cancelled
Build and Push Images / build-strixhalo (push) Has been cancelled
Build and Push Images / build-intel (push) Has been cancelled
Build and Push Images / Release (push) Has been cancelled
Build and Push Images / Notify (push) Has been cancelled
Changes to the amdsmi-shim package should trigger image rebuilds.
2026-02-06 08:52:33 -05:00
5f1873908f overhaul image builds.
Some checks failed
Build and Push Images / determine-version (push) Successful in 5s
Build and Push Images / build-nvidia (push) Failing after 21s
Build and Push Images / build-rdna2 (push) Failing after 21s
Build and Push Images / build-strixhalo (push) Failing after 12s
Build and Push Images / build-intel (push) Failing after 19s
Build and Push Images / Release (push) Has been skipped
Build and Push Images / Notify (push) Successful in 1s
2026-02-06 07:47:37 -05:00
5606a9a626 fix: notify job and registry push issues
Some checks failed
Build and Push Images / determine-version (push) Waiting to run
Build and Push Images / build-nvidia (push) Has been cancelled
Build and Push Images / build-rdna2 (push) Has been cancelled
Build and Push Images / build-strixhalo (push) Has been cancelled
Build and Push Images / build-intel (push) Has been cancelled
Build and Push Images / Release (push) Has been cancelled
Build and Push Images / Notify (push) Has been cancelled
2026-02-05 06:04:09 -05:00
bc3c115b90 fix: Use internal HTTP endpoint with buildx config and direct auth
Some checks failed
Build and Push Images / determine-version (push) Successful in 1m24s
Build and Push Images / build-rdna2 (push) Failing after 3h11m33s
Build and Push Images / build-nvidia (push) Failing after 3h11m35s
Build and Push Images / build-intel (push) Failing after 17m53s
Build and Push Images / build-strixhalo (push) Failing after 3h11m34s
Build and Push Images / Release (push) Has been cancelled
Build and Push Images / Notify (push) Has been cancelled
- Back to internal endpoint (avoids Cloudflare 100MB limit)
- buildkitd-config-inline: http=true, insecure=true for HTTP registry
- Create ~/.docker/config.json directly with base64 auth
- No docker login command (it defaults to HTTPS)
- Buildx reads config.json for push authentication
2026-02-04 18:08:28 -05:00
dd6c400581 fix: Use external HTTPS endpoint with valid cert for registry
Some checks failed
Build and Push Images / determine-version (push) Successful in 54s
Build and Push Images / Release (push) Has been cancelled
Build and Push Images / Notify (push) Has been cancelled
Build and Push Images / build-strixhalo (push) Has been cancelled
Build and Push Images / build-intel (push) Has been cancelled
Build and Push Images / build-rdna2 (push) Has been cancelled
Build and Push Images / build-nvidia (push) Has been cancelled
Simplify approach - use git.daviestechlabs.io external endpoint
which has valid Let's Encrypt cert. Much cleaner than fighting
with HTTP/HTTPS issues on internal endpoints.

- Remove buildkitd-config-inline (not needed for valid HTTPS)
- Remove manual config.json creation
- Use standard docker/login-action for Gitea registry
2026-02-04 18:01:58 -05:00
a77d5db274 fix: Create docker config.json directly for buildx auth
Some checks failed
Build and Push Images / determine-version (push) Successful in 55s
Build and Push Images / Release (push) Has been cancelled
Build and Push Images / Notify (push) Has been cancelled
Build and Push Images / build-strixhalo (push) Has been cancelled
Build and Push Images / build-intel (push) Has been cancelled
Build and Push Images / build-rdna2 (push) Has been cancelled
Build and Push Images / build-nvidia (push) Has been cancelled
Bypass docker login command which requires daemon configuration.
Instead, create ~/.docker/config.json directly with base64 auth.
Buildx uses this config for registry authentication during push.
2026-02-04 17:53:02 -05:00
9e9a93b838 fix: Use internal HTTP endpoint for rootless DinD runner
Some checks failed
Build and Push Images / determine-version (push) Successful in 1m30s
Build and Push Images / build-nvidia (push) Failing after 6m24s
Build and Push Images / build-strixhalo (push) Failing after 5m14s
Build and Push Images / build-rdna2 (push) Failing after 6m54s
Build and Push Images / build-intel (push) Failing after 5m59s
Build and Push Images / Release (push) Has been skipped
Build and Push Images / Notify (push) Successful in 2s
- Switch from external HTTPS to internal HTTP (gitea-http.gitea.svc.cluster.local:3000)
- Remove sudo commands that don't work in rootless Docker-in-Docker
- Use direct docker login with --password-stdin for compatibility
- Add http=true to buildkitd config for HTTP registry
2026-02-04 15:27:53 -05:00
110d1eab55 fix: Configure Docker daemon for insecure registry before login
Some checks failed
Build and Push Images / determine-version (push) Successful in 53s
Build and Push Images / build-nvidia (push) Failing after 7m2s
Build and Push Images / build-rdna2 (push) Failing after 7m6s
Build and Push Images / Release (push) Has been cancelled
Build and Push Images / Notify (push) Has been cancelled
Build and Push Images / build-strixhalo (push) Has been cancelled
Build and Push Images / build-intel (push) Has been cancelled
The docker/login-action needs the registry marked as insecure in the
Docker daemon config, not just in buildkitd. This adds a step to
configure /etc/docker/daemon.json with insecure-registries before
attempting to login.
2026-02-04 15:18:06 -05:00
e299f6476e fix: Use external registry URL for proper Bearer token auth
Some checks failed
Build and Push Images / determine-version (push) Successful in 1m32s
Build and Push Images / build-nvidia (push) Failing after 6m47s
Build and Push Images / build-rdna2 (push) Failing after 7m8s
Build and Push Images / build-strixhalo (push) Failing after 6m35s
Build and Push Images / build-intel (push) Failing after 6m35s
Build and Push Images / Release (push) Has been skipped
Build and Push Images / Notify (push) Successful in 2s
Gitea's container registry uses Bearer token auth with realm pointing
to external URL. Changed from internal K8s service URL to
registry.lab.daviestechlabs.io for proper auth flow.

Also removed insecure registry buildx config since using HTTPS now.
2026-02-04 08:13:35 -05:00
5cb79a0fe7 fix: Use docker/login-action for buildx registry authentication
Some checks failed
Build and Push Images / determine-version (push) Successful in 57s
Build and Push Images / build-nvidia (push) Failing after 6m47s
Build and Push Images / build-rdna2 (push) Failing after 7m10s
Build and Push Images / Release (push) Has been cancelled
Build and Push Images / Notify (push) Has been cancelled
Build and Push Images / build-intel (push) Has been cancelled
Build and Push Images / build-strixhalo (push) Has been cancelled
docker login doesn't properly propagate credentials to buildx builders.
docker/login-action handles this correctly and creates proper ~/.docker/config.json
2026-02-04 08:00:12 -05:00
338b668388 feat: Add semantic versioning based on commit message prefixes
Some checks failed
Build and Push Images / determine-version (push) Successful in 55s
Build and Push Images / build-nvidia (push) Failing after 1h52m48s
Build and Push Images / build-rdna2 (push) Failing after 3h14m40s
Build and Push Images / build-strixhalo (push) Failing after 1h52m42s
Build and Push Images / build-intel (push) Failing after 3h14m39s
Build and Push Images / Release (push) Has been cancelled
Build and Push Images / Notify (push) Has been cancelled
- Added determine-version job that runs BEFORE builds
- Version bump based on commit message:
  - major: or BREAKING CHANGE → major bump
  - minor:, feat:, or feature: → minor bump
  - everything else → patch bump
- All build jobs now depend on determine-version
- Images tagged with calculated version (e.g. v1.2.3) + latest
- Release job creates git tag after successful builds
- Notify job includes version info in notifications
- PRs get tagged with pr-<number>
- Manual tag pushes use tag directly (no version recalculation)
2026-02-03 22:30:48 -05:00
96921fe799 fix: workflow conditions for push events
Some checks failed
Build and Push Images / build-nvidia (push) Failing after 15s
Build and Push Images / build-rdna2 (push) Failing after 17s
Build and Push Images / build-strixhalo (push) Failing after 15s
Build and Push Images / build-intel (push) Failing after 16s
Build and Push Images / Release (push) Has been skipped
Build and Push Images / Notify (push) Successful in 1s
The if conditions were checking github.event.inputs.image == '' which
fails for push events where inputs is undefined. Changed logic to run
all builds unless this is a workflow_dispatch with a specific image
selected.
2026-02-03 21:39:17 -05:00
8af9d04210 fix(ci): configure Docker buildx for insecure HTTP registry
Some checks failed
Build and Push Images / build-nvidia (push) Failing after 6m6s
Build and Push Images / build-rdna2 (push) Failing after 6m31s
Build and Push Images / build-strixhalo (push) Failing after 5m35s
Build and Push Images / build-intel (push) Failing after 5m33s
Build and Push Images / Release (push) Has been skipped
Build and Push Images / Notify (push) Successful in 1s
2026-02-02 17:21:39 -05:00
456f08ec81 fix: use internal K8s service URL for container registry
Some checks failed
Build and Push Images / build-rdna2 (push) Failing after 8m19s
Build and Push Images / build-nvidia (push) Failing after 9m26s
Build and Push Images / build-strixhalo (push) Failing after 6m50s
Build and Push Images / build-intel (push) Failing after 7m14s
Build and Push Images / Release (push) Has been skipped
Build and Push Images / Notify (push) Successful in 1s
- Switch from external git.daviestechlabs.io to internal gitea-http.gitea.svc
- Avoids Cloudflare/Authentik routing since runner is in-cluster
- Add REGISTRY_HOST env var for login steps
2026-02-02 13:28:51 -05:00
16f6199534 ci: add [skip images] support and trigger ray-serve publish
Some checks failed
Build and Push Images / build-nvidia (push) Has been skipped
Build and Push Images / build-intel (push) Has been skipped
Build and Push Images / build-rdna2 (push) Has been skipped
Build and Push Images / build-strixhalo (push) Has been skipped
Build and Push Images / Release (push) Has been skipped
Build and Push Images / Notify (push) Successful in 1s
Build and Publish ray-serve-apps / lint (push) Failing after 3m38s
Build and Publish ray-serve-apps / publish (push) Has been skipped
[ray-serve only]

- Add skip conditions to all image build jobs
- Commit message [skip images] or [ray-serve only] skips image builds
- Touch ray_serve/__init__.py to trigger publish workflow
2026-02-02 11:02:12 -05:00
bf93c5d7f4 ci: add path filters to avoid building images on ray-serve changes
Some checks failed
Build and Push Images / build-strixhalo (push) Has been cancelled
Build and Push Images / build-intel (push) Has been cancelled
Build and Push Images / Release (push) Has been cancelled
Build and Push Images / Notify (push) Has been cancelled
Build and Push Images / build-rdna2 (push) Has been cancelled
Build and Push Images / build-nvidia (push) Has been cancelled
Only trigger image builds when dockerfiles/ changes.
ray-serve package changes now only trigger publish-ray-serve.yaml.
2026-02-02 10:59:17 -05:00
876188a150 feat: add ntfy notifications and semantic versioning (ADR-0015)
Some checks failed
Build and Push Images / build-nvidia (push) Failing after 26s
Build and Push Images / build-strixhalo (push) Failing after 34s
Build and Push Images / build-rdna2 (push) Failing after 47s
Build and Push Images / build-intel (push) Failing after 23s
Build and Push Images / Release (push) Has been skipped
Build and Push Images / Notify (push) Successful in 1s
2026-02-02 08:00:33 -05:00
e1529ad923 ci: fix registry login - skip on PRs, add Docker Hub auth
Some checks failed
Build and Push Images / build-nvidia (push) Failing after 31s
Build and Push Images / build-rdna2 (push) Failing after 33s
Build and Push Images / build-strixhalo (push) Failing after 20s
Build and Push Images / build-intel (push) Failing after 25s
- Only login to Gitea registry on push (not PRs)
- Add optional Docker Hub login to avoid pull rate limits
- Requires REGISTRY_USER, REGISTRY_TOKEN secrets in Gitea
- Optional: DOCKERHUB_USERNAME (var) + DOCKERHUB_TOKEN (secret)
2026-02-02 07:35:20 -05:00
a16ffff73f feat: Add GPU-specific Ray worker images with CI/CD
Some checks failed
Build and Push Images / build-nvidia (push) Failing after 1s
Build and Push Images / build-rdna2 (push) Failing after 1s
Build and Push Images / build-strixhalo (push) Failing after 1s
Build and Push Images / build-intel (push) Failing after 1s
- Add Dockerfiles for nvidia, rdna2, strixhalo, and intel GPU targets
- Add ray-serve modules (embeddings, whisper, tts, llm, reranker)
- Add Gitea Actions workflow for automated builds
- Add Makefile for local development
- Update README with comprehensive documentation
2026-02-01 15:04:31 -05:00