Integrate Backstage with the shared Bun CI/CD workflows #62

Open
opened 2026-11-22 13:23:50 +00:00 by martin · 0 comments
Owner

Summary

Integrate Backstage with the shared Bun CI/CD approach so a validated application build publishes a versioned image and opens a GitOps promotion PR, without deploying directly from application CI.

Context

  • #22 supplies repository-owned quality checks. #48 separately covers CI image/caching optimization.
  • Backstage is a Bun workspace but is not Astro. The shared bun-astro rule was intentionally narrowed by Personal/nixos-configuration#68; do not opt Backstage into Astro-only validation.
  • Personal/nixos-configuration#71 tracks the Backstage-compatible shared workflow path.
  • Personal/cluster#88 defines the dev/prod Nixidy application targets. #30 is the overall hosting gate.

Scope

  • Adopt the shared Bun validation → image publication → cluster promotion pattern for Backstage, coordinating with the global workflow issue rather than copying Astro workflows or adding a parallel deployment system.
  • Preserve the repository's supported Bun and Node versions and native-module ABI requirements.
  • Publish a reproducible, versioned OCI image to the Forgejo registry only after the Backstage checks pass.
  • Create or update a PR in Personal/cluster to promote the image to the correct environment. The PR merge and ArgoCD reconciliation—not the application pipeline—perform deployment.
  • Keep registry and cluster-repository credentials in Woodpecker secrets.

Acceptance criteria

  • Backstage receives the Backstage-compatible global workflow path from Personal/nixos-configuration#71 and does not receive Astro-only commands.
  • The existing Backstage validation checks gate image publication; the production image uses the supported Node 24 runtime and is smoke-tested from the same build artifact.
  • A successful default-branch build publishes a versioned dev image; a version-tagged release publishes the corresponding production image, following the shared Bun workflow convention.
  • Image promotion creates or updates a reviewable PR against the correct dev/prod application in Personal/cluster#88; unchanged image references do not create redundant PRs.
  • CI does not update the cluster's main branch or deploy directly; ArgoCD deploys only the merged GitOps change.
  • Registry and Forgejo write credentials are supplied through Woodpecker secrets and do not appear in source files or logs.
  • Pipeline evidence verifies validation gating, image publication, and PR creation for the Backstage workflow path.

Dependencies

## Summary Integrate Backstage with the shared Bun CI/CD approach so a validated application build publishes a versioned image and opens a GitOps promotion PR, without deploying directly from application CI. ## Context - [#22](https://code.martials.no/Personal/backstage/issues/22) supplies repository-owned quality checks. [#48](https://code.martials.no/Personal/backstage/issues/48) separately covers CI image/caching optimization. - Backstage is a Bun workspace but is not Astro. The shared `bun-astro` rule was intentionally narrowed by [Personal/nixos-configuration#68](https://code.martials.no/Personal/nixos-configuration/issues/68); do not opt Backstage into Astro-only validation. - [Personal/nixos-configuration#71](https://code.martials.no/Personal/nixos-configuration/issues/71) tracks the Backstage-compatible shared workflow path. - [Personal/cluster#88](https://code.martials.no/Personal/cluster/issues/88) defines the dev/prod Nixidy application targets. [#30](https://code.martials.no/Personal/backstage/issues/30) is the overall hosting gate. ## Scope - Adopt the shared Bun validation → image publication → cluster promotion pattern for Backstage, coordinating with the global workflow issue rather than copying Astro workflows or adding a parallel deployment system. - Preserve the repository's supported Bun and Node versions and native-module ABI requirements. - Publish a reproducible, versioned OCI image to the Forgejo registry only after the Backstage checks pass. - Create or update a PR in Personal/cluster to promote the image to the correct environment. The PR merge and ArgoCD reconciliation—not the application pipeline—perform deployment. - Keep registry and cluster-repository credentials in Woodpecker secrets. ## Acceptance criteria - [ ] Backstage receives the Backstage-compatible global workflow path from Personal/nixos-configuration#71 and does not receive Astro-only commands. - [ ] The existing Backstage validation checks gate image publication; the production image uses the supported Node 24 runtime and is smoke-tested from the same build artifact. - [ ] A successful default-branch build publishes a versioned dev image; a version-tagged release publishes the corresponding production image, following the shared Bun workflow convention. - [ ] Image promotion creates or updates a reviewable PR against the correct dev/prod application in Personal/cluster#88; unchanged image references do not create redundant PRs. - [ ] CI does not update the cluster's main branch or deploy directly; ArgoCD deploys only the merged GitOps change. - [ ] Registry and Forgejo write credentials are supplied through Woodpecker secrets and do not appear in source files or logs. - [ ] Pipeline evidence verifies validation gating, image publication, and PR creation for the Backstage workflow path. ## Dependencies - Personal/nixos-configuration#71 — add the Backstage-compatible shared Bun workflow path. - Personal/cluster#88 — provide the dev/prod Nixidy deployment targets. - #22 — completed repository-owned application quality gates.
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#62
No description provided.