Context
The Build API already provides a build history endpoint (BuildHistoryResponse) and stage-level status on each BuildJob. Surface this in the console for at-a-glance progress and historical trends.
Depends on: #44 (scaffold), #45 (detail page)
Scope
Stage Progress (on BuildJob detail page)
Build History Tab
Data Sources
Stage status from the K8s resource:
{
"stages": [
{ "name": "fetch", "state": "Succeeded" },
{ "name": "build", "state": "Running" },
{ "name": "package", "state": "Pending" }
]
}
History from Build API:
{
"buildJob": "body-ecu-nucleo",
"entries": [
{ "run": 3, "phase": "Succeeded", "startedAt": "...", "duration": "2m34s", "commitSHA": "abc123" }
]
}
Context
The Build API already provides a build history endpoint (
BuildHistoryResponse) and stage-level status on each BuildJob. Surface this in the console for at-a-glance progress and historical trends.Depends on: #44 (scaffold), #45 (detail page)
Scope
Stage Progress (on BuildJob detail page)
spec.stages/status.stages)ProgressStepperor custom step componentBuild History Tab
/builds/{name}/historyendpointData Sources
Stage status from the K8s resource:
{ "stages": [ { "name": "fetch", "state": "Succeeded" }, { "name": "build", "state": "Running" }, { "name": "package", "state": "Pending" } ] }History from Build API:
{ "buildJob": "body-ecu-nucleo", "entries": [ { "run": 3, "phase": "Succeeded", "startedAt": "...", "duration": "2m34s", "commitSHA": "abc123" } ] }