Skip to content
anythingai.space
Deployment & Deliveryintermediate12 min · 9 steps

CI/CD Pipelines

Verify every change — including prompts, models and retrieval settings — and release it in safe, gradual, reversible steps.

merge→prod48h
time to restorehours
deploysweekly
Codeunit-testedPrompt edituntestedModel versionuntestedRe-indexed KBuntestedProduction 100%1 in 5 releases
requesterrordatasignal
metrics are illustrative
1 / 9
ProblemStep 1 of 9

Behaviour changes that never touch the code

The assistant ships weekly, by hand. A release takes about two days from merge to production, roughly one in five releases causes an incident, and restoring service takes hours (illustrative).

Worse, the riskiest changes aren't code at all: a reworded prompt, a new model version, a different top-k, a re-indexed knowledge base. Unit tests don't see any of them.

Watch outIf only code goes through the pipeline, the changes most likely to alter answers bypass every check.

Lesson 4 of 20 in Deployment & Delivery