sean/pipelines
Watch
1
0
Fork
You've already forked pipelines
 0
Code Issues Pull requests 12 Projects Releases 291 Packages Wiki Activity
291 releases 291 tags
  • v0.1.59 797d2a55b3

    v0.1.59 Stable

    gitea_admin released this 2026-07-05 15:42:52 +00:00 | 1060 commits to main since this release

    Changed

    • Trace/status now delegate to the query service — the client-side join is deleted (Phase B). The
      dashboard SPA and pipectl each carried their own copy of the Build→Release→Deploy join (JS in
      dashboard.html, inline python in bin/pipectl), plus a duplicated Forgejo compare "first release
      containing" walk. Both now call the ONE server-side join in the pipelines query service (embedded in
      pipelines-operator): the SPA via a new same-origin /pipeapi/ nginx proxy (mirrors /relapi/,
      GET-only, in-cluster plain-HTTP to pipelines-operator-query...svc:9090), pipectl via the apiserver
      service-proxy (RBAC-gated by the existing kubeconfig — no Forgejo reachability or CA trust needed from
      the laptop). Deleted traceMatch/resolveTraceSha/traceContaining (SPA) and the inline python
      join + trace_version_sha (pipectl); the SPA keeps a pure traceHtml renderer, pipectl keeps only
      local file:line→sha git blame (the server has no working tree). Payoff: cross-project trace —
      a deploy's carrierSha is now followed into the seanfarm carrier commit and rendered as a carrier
      leg, the capability no single-project client could do. tests/dashboard-change-trace.test.js
      rewritten to exercise the renderer + assert the /pipeapi/ wiring.

    Included changes (v0.1.58 -> v0.1.59)

    • cebfedbb517d Merge remote-tracking branch 'origin/trunk' into feat/phase-b-query-service-repoint
    • cb34a53f1246 feat(dashboard,pipectl): repoint trace/status to the query service (Phase B)
    Downloads