How to Grow Your Internal Backstage Community with Some Ope...
summary
Backstage community tooling and concrete fixes that save time: using backstage/actions yarn-install drops yarn install from 1m27s to 13s; running backstage-repo-tools generate-catalog-info produces catalog-info.yaml per plugin so ownership and health checks surface a wrong-React-version issue; adding the backstage:carrot yarn plugin lets a repo use logical Backstage versions instead of exact numbers; run a plugin’s --link dev entry point or yarn start for fast hot reload and link local open-source core for live upstream testing, plus OpenAPI wrapServer enforces runtime contract in tests.
AI-written summary · about
chapters (17)
- 0:00Intro
- 0:16Introductions
- 1:22Continuous integration
- 4:04Use the catalog
- 6:22Updating Backstage
- 8:06Yarn Plugin
- 9:34Backstage Plugin
- 9:49Demo
- 11:43Free Dev Entry Point
- 12:08Example Change
- 14:06Benefits
- 14:22Contexts
- 15:34Panic
- 15:46Open API File
- 19:15Confidence in Integration
- 19:27Wrap Up
- 20:16Questions
related talks
34mPanel: Building a Healthy Backstage Plugins Ecosystem
35mBackstage: Restoring Order To Your Chaos
26mBackstage Plugin Development: Tales from the Trenches
47mImproving Developer Experience with Backstage
35mImproving Developer Experience with Open Source 1
27mIntroduction to Backstage
22mUnlocking Backstage’s Potential: Driving Adoption and Maturity With Your Develope...
11mBackstage Plugins Made Simple: No Rebuild Needed