Show Woodpecker delivery status for catalog components #29

Open
opened 2026-11-07 21:51:25 +00:00 by martin · 0 comments
Owner

Goal

Start with a small CI integration rather than a general deployment dashboard.

Acceptance criteria

  • Define repository-to-Woodpecker mapping through catalog metadata.
  • Show the latest relevant pipeline status with a link to its run.
  • Distinguish application validation from automated review and other workflows; do not label a review failure as a deployment failure.
  • Handle missing CI, unavailable APIs, and access restrictions gracefully.
  • Keep API credentials backend-side and enforce intended visibility for private repositories.

Depends on

Repository-owned catalog metadata.

Phase

2 — Useful developer workflows

## Goal Start with a small CI integration rather than a general deployment dashboard. ## Acceptance criteria - [ ] Define repository-to-Woodpecker mapping through catalog metadata. - [ ] Show the latest relevant pipeline status with a link to its run. - [ ] Distinguish application validation from automated review and other workflows; do not label a review failure as a deployment failure. - [ ] Handle missing CI, unavailable APIs, and access restrictions gracefully. - [ ] Keep API credentials backend-side and enforce intended visibility for private repositories. ## Depends on Repository-owned catalog metadata. ## Phase 2 — Useful developer workflows
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
Personal/backstage#29
No description provided.