ci(ci): hermetic AI report deployment profile and Ollama entrypoint - #362
Merged
Conversation
GiZano
force-pushed
the
chore/ci-ai-profile
branch
from
August 5, 2026 21:40
8758ae8 to
1e2c961
Compare
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Deploys the on-premise AI Emergency Report stack (v1.2.0) while keeping CI fully hermetic — the default
docker compose upand CI pipelines never pull a model.Changes
docker-compose.yml— addsollama(local LLM, model auto-pulled on startup, healthcheck) andai-worker(dedicated report consumer) services, both gated behind the newaicompose profile. The mainworkerservice receivesAI_REPORT_ENABLED.init-scripts/ollama-entrypoint.sh— serves Ollama, waits for readiness, then pulls$OLLAMA_MODEL(defaultllama3.2:1b).backend-ci.yml— setsAI_REPORT_ENABLED=falsefor CI so the stress/integration pipeline avoids orphan report enqueueing.Why a profile?
Pulling
llama3.2:1b(~1.8 GB) on every CI run is slow and heavy. Theaiprofile keeps default startup lightweight; operators opt in viadocker compose --profile ai up -d.Verification
docker compose config --quiet→ valid