Use a Bun image and caching for CI setup #48

Open
opened 2026-11-21 12:09:11 +00:00 by martin · 0 comments
Owner

Summary

Use a pinned Bun-based container image for CI steps that currently start from Node and bootstrap Bun, and use caching where supported to reduce repeated setup and dependency-install time.

Context

The repository-owned workflow is .woodpecker/application-checks.yaml. It currently uses Node images and downloads pinned Bun 1.4.4 into the workspace during dependency installation. Bun is already the package manager and script runner; Node remains important for Backstage and native modules such as better-sqlite3. The image change must not cause a Node ABI mismatch between installation and later steps.

Scope

  • Replace the Node-image-plus-Bun-bootstrap pattern with an appropriately pinned Bun image for CI steps that use Bun, where compatible.
  • Avoid downloading/installing Bun during each pipeline run when the image already supplies the required pinned version.
  • Configure or reuse dependency/build caching supported by the workflow, and compare representative cold and warm pipeline timings.
  • Keep any Node execution needed by Backstage, tests, or native modules on a compatible Node version and ABI.

Out of scope

  • Changing the production runtime or Docker image as part of this CI optimization.
  • Upgrading Bun or unrelated dependencies.

Acceptance criteria

  • The workflow uses a pinned Bun image for compatible Bun install/script steps and no longer bootstraps Bun from the network in those steps.
  • The complete application-checks workflow passes, including better-sqlite3, unit tests, builds, and E2E.
  • Node-dependent steps use compatible Node and native-module ABIs, with no cross-step ABI mismatch.
  • A supported cache is configured and shown to be reused on a subsequent run.
  • Cold and warm timings are compared with the current workflow to verify whether the change improves performance.
  • The README and repository guidance reflect the resulting CI toolchain, if it differs from the documented setup.
  • #20 (Bun package-manager migration)
  • #47 (temporary Node 22 pin and planned runtime upgrade; related CI toolchain work, not a prerequisite)
## Summary Use a pinned Bun-based container image for CI steps that currently start from Node and bootstrap Bun, and use caching where supported to reduce repeated setup and dependency-install time. ## Context The repository-owned workflow is .woodpecker/application-checks.yaml. It currently uses Node images and downloads pinned Bun 1.4.4 into the workspace during dependency installation. Bun is already the package manager and script runner; Node remains important for Backstage and native modules such as better-sqlite3. The image change must not cause a Node ABI mismatch between installation and later steps. ## Scope - Replace the Node-image-plus-Bun-bootstrap pattern with an appropriately pinned Bun image for CI steps that use Bun, where compatible. - Avoid downloading/installing Bun during each pipeline run when the image already supplies the required pinned version. - Configure or reuse dependency/build caching supported by the workflow, and compare representative cold and warm pipeline timings. - Keep any Node execution needed by Backstage, tests, or native modules on a compatible Node version and ABI. ## Out of scope - Changing the production runtime or Docker image as part of this CI optimization. - Upgrading Bun or unrelated dependencies. ## Acceptance criteria - [ ] The workflow uses a pinned Bun image for compatible Bun install/script steps and no longer bootstraps Bun from the network in those steps. - [ ] The complete application-checks workflow passes, including better-sqlite3, unit tests, builds, and E2E. - [ ] Node-dependent steps use compatible Node and native-module ABIs, with no cross-step ABI mismatch. - [ ] A supported cache is configured and shown to be reused on a subsequent run. - [ ] Cold and warm timings are compared with the current workflow to verify whether the change improves performance. - [ ] The README and repository guidance reflect the resulting CI toolchain, if it differs from the documented setup. ## Related - #20 (Bun package-manager migration) - #47 (temporary Node 22 pin and planned runtime upgrade; related CI toolchain work, not a prerequisite)
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.

Dependencies

No dependencies set

Reference
Personal/backstage#48
No description provided.