Add application quality gates to Woodpecker #22
Labels
No labels
automerge
bug
dependencies
duplicate
help wanted
invalid
lang
rust
migrations
opencode
question
security
type
documentation
type
enhancement
type
maintenance
type
refactor
vulnerability
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Blocks
Depends on
#20 Replace Yarn with Bun before hosted deployment
Personal/backstage
#30 Establish a secure, persistent hosted deployment
Personal/backstage
#21 Establish a reproducible dependency and test baseline
Personal/backstage
#34 Update all dependencies
Personal/backstage
Reference
Personal/backstage#22
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Goal
Add repository-owned application validation alongside existing global workflows.
Evidence
Woodpecker pipeline 56 ran automated PR review, which failed while parsing a changed-files API response. Its resolved configuration contained global review, release, Renovate validation, and scheduled flake-health workflows, but no Backstage build/test checks. This is not evidence of an application build failure.
Acceptance criteria
Scope
Repository-owned configuration only; changing shared global workflows is outside this issue.
Phase
1 — Trustworthy foundation
Vault context: reuse shared CI where compatible
See
projects/nixos/woodpecker-global-workflow-architecture.md. Existing policy deliberately injects shared workflows and preserves repository-owned workflows. Prefer compatible shared stages plus Backstage-specific supplemental checks rather than duplicating global policy.The documented
bun-astrorule matchesbun.lockandpackage.json; its verification runs Astro checks/Biome and its publication/promotion stages have persistent effects. Coordinate with #20 and inspect the current rule and resolved pipeline configuration. Adding Bun must not be assumed to provide suitable Backstage quality gates or safe deployment behavior. Global validation documented here also has different event triggers from the proposed PR checks.Keep changes in this repository unless separate infrastructure work is explicitly agreed.
Implemented in #41 (
ci/quality-gates-22), which closes this issue on merge.What was added
.woodpecker/application-checks.yaml, a repository-owned workflow triggered on pull requests and default-branch pushes (excluding Markdown and the generated catalog file).node:24-trixieusing the checked-in Yarn 4.18.1 release: immutable install (with Python 3), typecheck, lint, formatting, unit tests, and backend build.timeoutand prints a dedicated message when it is exceeded.FORGEJO_TOKENand nosync:forgejo, so validation is independent of live Forgejo data.README.mddocuments the CI setup and its boundary from global workflows;AGENTS.mdrecords the maintenance constraint.Evidence
woodpecker-cli lint .woodpecker/application-checks.yaml— valid.application-checksand the globalpr-reviewworkflows.application-checkssucceeded with every step green: install, typecheck, lint, formatting, unit tests, backend build.The Bun migration of install/script invocation remains with #20.