Release pipeline

Azure Pipelines / Actions / Jenkins: checkout with credentials, install Go, build navo, scan trees, validate, optional push.

• ✓Clear role in the CI / release zone of the mapEditDelete
• ✓Topology and narrative stay in versioned architecture YAMLEditDelete
• ✓Visible to unlimited viewers without a platform portal seatEditDelete

Who

Edit

CI / release owners and on-call for Release pipeline

What

Edit

Post-merge job that builds tooling and refreshes maps.

When

Edit

Continuous — part of the always-on architecture map

Where

Edit

CLI pipeline automation · CI / release

Why

Edit

Documents how Release pipeline connects in the living map so teams share one Git-backed model.

• main branch← triggers
• Navo CLI→ runs

• release-pipeline-service
• pipeline-platform

• Release pipeline runbook

  wiki/wiki/release-pipeline.md

  In-app wiki path (demo stub)

  EditDelete

• Source repository

  repohttps://example.com/repos/release-pipeline

  Example repo link for the public demo

  EditDelete

• Ops dashboard

  urlhttps://example.com/dashboards/release-pipeline

  EditDelete

In the full Navo app (local pnpm dev), this form writes links into architecture YAML. On the public website it is disabled.

In Navo, notes and personal links stay in browser localStorage until you export for a PR. Overlay editing is off in this public demo.