Add a Backstage-compatible global Bun CI/CD path #71
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
#62 Integrate Backstage with the shared Bun CI/CD workflows
Personal/backstage
Reference
Personal/nixos-configuration#71
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?
Summary
Add a selectively matched, Backstage-compatible path to the shared Bun CI/CD workflows: validate the application, publish a pinned OCI image, then open a GitOps promotion PR in the cluster repository.
Context
The shared
bun-astrorule was intentionally narrowed in #68 to require an Astro config because the existing global verify step runs Astro-only commands. Backstage is a Bun workspace but is not an Astro application; do not broaden that rule or inject Astro checks into it.The existing global Bun flow is the desired model: verification gates image publication, then a deployment workflow opens or updates a cluster promotion PR. However, the current workflow set is Astro-oriented, builds through
.#image-$ENV, and its deploy workflow assumes the oldmartin/clusterrepository path. Backstage's repository-owned validation is tracked in Personal/backstage#22, and the cluster target is now Personal/cluster.Scope
Personal/clusterfor the appropriate dev/prod Nixidy application. ArgoCD remains the deployment mechanism after the PR is merged; CI must not deploy directly to the cluster.Acceptance criteria
Personal/clusterdev or prod application, skipping unchanged updates.Related