5364cc9666
The script demanded JENKINS_USER and JENKINS_TOKEN in the environment and said only 'set JENKINS_USER' when they were missing, which is not enough to act on. It now sources scripts/ops/hermes_triage_demo.env, git-ignored so it can hold real tokens, and names that file when credentials are absent. An example file records what belongs in it. The fixture command also still polled for a hermes-demo-repair-<build> Job. That Job stopped existing when the repair became an in-process ConfigMap patch, so the command would have waited its full 400 seconds and then reported nothing. It now watches the fixture returning to healthy, which is what actually happens. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
16 lines
675 B
Plaintext
16 lines
675 B
Plaintext
# Copy to hermes_triage_demo.env (same directory) and fill in.
|
|
# That filename is git-ignored so it can hold real tokens.
|
|
|
|
# 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"
|
|
|
|
# Gitea token, used only to report open pull requests during preflight.
|
|
# Preflight still works without it; that one line will read "?".
|
|
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"
|