From a9fff9e46b4062c7e690a9b95b89665169c1067b Mon Sep 17 00:00:00 2001 From: jenkins Date: Thu, 6 Aug 2026 06:50:35 -0300 Subject: [PATCH] docs: junit and pipeline-stage-view are live; record why it was never blocked Co-Authored-By: Claude Opus 5 --- knowledge/hermes-automated-triage-24h-plan.md | 33 ++++++++++++++----- .../hermes-automated-triage-24h-plan.md | 33 ++++++++++++++----- 2 files changed, 50 insertions(+), 16 deletions(-) diff --git a/knowledge/hermes-automated-triage-24h-plan.md b/knowledge/hermes-automated-triage-24h-plan.md index f8ba34661..bf798a0b5 100644 --- a/knowledge/hermes-automated-triage-24h-plan.md +++ b/knowledge/hermes-automated-triage-24h-plan.md @@ -1141,14 +1141,31 @@ Real homegrown service diagnoses (no action allowlisted, all escalated): - **Fixture storage**: the demo fixture is a ConfigMap, not a PVC. Longhorn attach latency and per-node engine availability made a PVC unreliable for a fast repeatable demo. -- **JUnit evidence**: this Jenkins has no `junit` publisher and no - `pipeline-stage-view` plugin, so `testReport` and `wfapi` return 404 for - every job. `failed_tests` and `first_failed_stage` are therefore always - empty. Console text is the only structured evidence, which drove the - failure-region extractor. Adding those two plugins (the current `junit` - release needs core 2.533; Jenkins here is 2.528.3, so a back-pin is - required) is the largest remaining quality improvement and needs a - Jenkins restart — deliberately not done the night before a demo. +- **JUnit evidence**: RESOLVED 2026-08-06. `junit 1369.v15da_00283f06` and + `pipeline-stage-view 2.41` are installed and active, with `scm-api` bumped + 724 -> 728 as their `workflow-cps` requires. This was never actually blocked + on a core upgrade: only the *latest* `junit` (1418) needs core 2.533, while + 1369 needs 2.504.3 and runs on 2.528.3. The earlier record was wrong because + it read the plugin's latest release rather than the + `dynamic-stable-2.528.3` update-center channel. + + `testReport` and `wfapi` now return 200 where they returned 404 all night - + `ariadne` build 414 reports 1183 passing tests through the API. No Ariadne + change was needed: the evidence collector already fetched + `testReport/api/json` and had simply always received a 404, so + `failed_tests` now populates on its own. + + This removes the *cause* of both diagnosis defects fixed the same day. With + no structured test data, console text was the only evidence, which is why + the enforced failure could be crowded out of the byte budget and why the + patcher could not locate a source file the console never named. + + Cost: installing them required restarting the controller, which rescheduled + it onto a node without the image cached and produced a ~15 minute outage on + the image pull alone, plus three killed builds. Pre-pull the controller + image on the worker nodes before any future Jenkins restart; the agent image + had already been pre-pulled for exactly this reason and the lesson was not + carried across. - **Multibranch jobs are not detected**: folder-style jobs expose a null `lastBuild` at the job root. - **OpenSearch namespace** is still pinned to the demo namespace plus diff --git a/services/comms/knowledge/hermes-automated-triage-24h-plan.md b/services/comms/knowledge/hermes-automated-triage-24h-plan.md index f8ba34661..bf798a0b5 100644 --- a/services/comms/knowledge/hermes-automated-triage-24h-plan.md +++ b/services/comms/knowledge/hermes-automated-triage-24h-plan.md @@ -1141,14 +1141,31 @@ Real homegrown service diagnoses (no action allowlisted, all escalated): - **Fixture storage**: the demo fixture is a ConfigMap, not a PVC. Longhorn attach latency and per-node engine availability made a PVC unreliable for a fast repeatable demo. -- **JUnit evidence**: this Jenkins has no `junit` publisher and no - `pipeline-stage-view` plugin, so `testReport` and `wfapi` return 404 for - every job. `failed_tests` and `first_failed_stage` are therefore always - empty. Console text is the only structured evidence, which drove the - failure-region extractor. Adding those two plugins (the current `junit` - release needs core 2.533; Jenkins here is 2.528.3, so a back-pin is - required) is the largest remaining quality improvement and needs a - Jenkins restart — deliberately not done the night before a demo. +- **JUnit evidence**: RESOLVED 2026-08-06. `junit 1369.v15da_00283f06` and + `pipeline-stage-view 2.41` are installed and active, with `scm-api` bumped + 724 -> 728 as their `workflow-cps` requires. This was never actually blocked + on a core upgrade: only the *latest* `junit` (1418) needs core 2.533, while + 1369 needs 2.504.3 and runs on 2.528.3. The earlier record was wrong because + it read the plugin's latest release rather than the + `dynamic-stable-2.528.3` update-center channel. + + `testReport` and `wfapi` now return 200 where they returned 404 all night - + `ariadne` build 414 reports 1183 passing tests through the API. No Ariadne + change was needed: the evidence collector already fetched + `testReport/api/json` and had simply always received a 404, so + `failed_tests` now populates on its own. + + This removes the *cause* of both diagnosis defects fixed the same day. With + no structured test data, console text was the only evidence, which is why + the enforced failure could be crowded out of the byte budget and why the + patcher could not locate a source file the console never named. + + Cost: installing them required restarting the controller, which rescheduled + it onto a node without the image cached and produced a ~15 minute outage on + the image pull alone, plus three killed builds. Pre-pull the controller + image on the worker nodes before any future Jenkins restart; the agent image + had already been pre-pulled for exactly this reason and the lesson was not + carried across. - **Multibranch jobs are not detected**: folder-style jobs expose a null `lastBuild` at the job root. - **OpenSearch namespace** is still pinned to the demo namespace plus