ci: cap the warm agent at one and shorten its idle time
Keeping the pod alive for an hour left two idle demo agents holding slots in a pool of five. That starves real CI, and would eventually starve this demo too by leaving nothing free when a build actually needs to run. Fifteen minutes covers a demo session - a warm-up run and then the real one - without parking capacity overnight for nobody, and instanceCap stops a second agent existing at all. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
parent
50372edd26
commit
b58cc90912
8
Jenkinsfile
vendored
8
Jenkinsfile
vendored
@ -19,7 +19,13 @@ podTemplate(
|
|||||||
// template mints a random POD_LABEL per build, so every build necessarily
|
// template mints a random POD_LABEL per build, so every build necessarily
|
||||||
// got a fresh pod.
|
// got a fresh pod.
|
||||||
label: 'hermes-code-demo-agent',
|
label: 'hermes-code-demo-agent',
|
||||||
idleMinutes: 60,
|
// Short, and capped at one. An earlier hour of idle time meant two warm
|
||||||
|
// agents sat holding slots in a pool of five, which starves real CI and
|
||||||
|
// would eventually starve this demo too. Fifteen minutes covers a demo
|
||||||
|
// session - warm-up run, then the real one - without parking capacity
|
||||||
|
// overnight for nobody.
|
||||||
|
idleMinutes: 15,
|
||||||
|
instanceCap: 1,
|
||||||
yaml: """
|
yaml: """
|
||||||
apiVersion: v1
|
apiVersion: v1
|
||||||
kind: Pod
|
kind: Pod
|
||||||
|
|||||||
Loading…
x
Reference in New Issue
Block a user