8899b76d07
Some checks failed
Tests / Declarative: Post Actions failed: 2, passed: 142
wait_for_build slept before its first poll, so a build that had already finished still bought a full interval of silence. On stage that reads as the script having missed the result - the build goes red in Jenkins and the terminal sits there. Polling first and sleeping after removes it entirely: a finished build now returns in under a second, measured. The interval drops from ten seconds to three for the same reason. The wait is dead air in front of an audience and a Jenkins status read is cheap. The budget is now expressed in seconds rather than poll counts, so shortening the interval does not silently shorten the timeout. This is only the script's own latency. Ariadne's autotriage cron is * * * * *, so an incident still takes up to a minute to appear after a build fails, and no amount of polling here changes that. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
titan-iac
Flux-managed Kubernetes desired-state config for bstein.dev.
Canonical source URL:
ssh://git@scm.bstein.dev:2242/bstein/titan-iac.git
Scope
This repo contains cluster configuration consumed by Flux:
- platform/infrastructure manifests
- service manifests and kustomizations
- operational scripts for render/reconcile workflows
Apply model
I use Git + Flux as the source of truth and avoid manual in-cluster edits for durable changes.