refactor(demo): split the two demos into two scripts
One script with a 'fixture' and a 'code' subcommand meant the wrong subcommand
was always one word away, in front of an audience, with different blast radii
behind each: the triage demo touches only a ConfigMap, the code demo pushes to
a repository and deletes issues. Those should not share a command line.
Each demo is now its own driver with the same five verbs - monitor, reset,
preflight, run, status - so knowing one teaches the other. What they genuinely
share (credentials, Jenkins access, the tick reader, the lab-wide preflight
checks) moved to hermes_demo_lib.sh rather than being duplicated, because the
reason to split was clarity at the command line, not two copies of the same
helper drifting apart.
Each reset now covers only its own demo. The triage reset no longer reaches
into a Gitea repository it never writes to, and the code reset owns the
repository cleanup entirely.
The credentials file is now hermes_demo.env since both read it; the old
hermes_triage_demo.env is still sourced as a fallback so a filled-in file
keeps working, and both names stay git-ignored.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-06 21:59:23 -03:00
|
|
|
# Copy to hermes_demo.env (same directory) and fill in. That filename is
|
|
|
|
|
# git-ignored so it can hold real tokens. Both demo drivers read it:
|
|
|
|
|
# hermes_triage_demo.sh and hermes_code_demo.sh.
|
2026-08-06 15:45:15 -03:00
|
|
|
|
|
|
|
|
# Jenkins API token: https://ci.bstein.dev -> your user -> Configure -> API Token
|
|
|
|
|
export JENKINS_USER="your-jenkins-user"
|
|
|
|
|
export JENKINS_TOKEN="your-jenkins-api-token"
|
|
|
|
|
|
refactor(demo): split the two demos into two scripts
One script with a 'fixture' and a 'code' subcommand meant the wrong subcommand
was always one word away, in front of an audience, with different blast radii
behind each: the triage demo touches only a ConfigMap, the code demo pushes to
a repository and deletes issues. Those should not share a command line.
Each demo is now its own driver with the same five verbs - monitor, reset,
preflight, run, status - so knowing one teaches the other. What they genuinely
share (credentials, Jenkins access, the tick reader, the lab-wide preflight
checks) moved to hermes_demo_lib.sh rather than being duplicated, because the
reason to split was clarity at the command line, not two copies of the same
helper drifting apart.
Each reset now covers only its own demo. The triage reset no longer reaches
into a Gitea repository it never writes to, and the code reset owns the
repository cleanup entirely.
The credentials file is now hermes_demo.env since both read it; the old
hermes_triage_demo.env is still sourced as a fallback so a filled-in file
keeps working, and both names stay git-ignored.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-06 21:59:23 -03:00
|
|
|
# Gitea token. The code demo needs it to clear its own demo repository on
|
|
|
|
|
# reset and to report open pull requests during preflight; the triage demo
|
|
|
|
|
# touches no repository and works without it.
|
2026-08-06 15:45:15 -03:00
|
|
|
export GITEA_TOKEN="your-gitea-token"
|
|
|
|
|
|
|
|
|
|
# Override only if you are not pointing at the usual lab.
|
|
|
|
|
# export JENKINS_URL="https://ci.bstein.dev"
|
|
|
|
|
# export GITEA_URL="https://scm.bstein.dev"
|
|
|
|
|
# export CODE_REPO_DIR="$HOME/Development/hermes-code-demo"
|