Begin an Automation Journey on Software Delivery to Increase..
summary
Live demo shows a local Backstage instance created with the create-app CLI and run with yarn dev, then extended by installing a front-end + back-end announcement plugin; presenter counts ~200 community plugins. Software templates generate a GitLab repo, register the new component in the centralized catalog, push manifests to GUPs and Argo CD, and produce pipelines and running Kubernetes pods on OpenShift with Helm values injected; single-sign-on via Keycloak and image storage in Quay are used, and the process works end-to-end.
AI-written summary · about
chapters (17)
- 0:00Backstage introduction
- 1:50Developer challenges
- 3:56Platform engineering
- 4:39What Backstage is and its core components
- 7:10Software catalog deep dive
- 8:13Extending Backstage
- 9:35Self-service templates
- 10:18TechDocs for centralized technical documentation
- 11:21Demo: Local setup
- 13:27Demo: Adding plugins
- 17:08Local to enterprise Backstage
- 18:55Customizing Backstage
- 20:01App creation with templates
- 27:48How templates work
- 33:14Platform engineering best practices
- 35:20Backstage lessons learned
- 37:49Q&A
related talks
28mBuilding Open Developer Platforms with Backstage
27mIntroduction to Backstage
25mThe Developer Portal: Open the Gate to Productivity 🚀
59mDevelop Your Development Automation
22mStreamlining Cloud-Native Development with OpenShift and Backstage
43mPlatform Engineering 101: Building Developer Platforms
43m#PlatformEngineering 101 Building #InternalDeveloperPlatforms
47mImproving Developer Experience with Backstage