Coming Soon to a Cloud Near You: Multiple Buildpack Support
summary
Cloud Foundry now supports combining multiple buildpacks in one cf push by splitting compile into supply and finalize scripts, running each pack’s supply to populate separate dependency dirs and then finalizing with symlinks into a single droplet. It remains backward compatible (old buildpacks work), vendors can ship single-purpose supply buildpacks for APM or proprietary drivers, and operators can define buildpack groups to enforce checks. A multi-buildpack shim lets teams try it immediately without upgrading.
AI-written summary · about
chapters (8)
- 0:00Intro
- 0:49What is a Buildpack
- 4:08Multiple Buildpacks
- 6:09Why Multiple Buildpacks
- 7:15Compatibility
- 7:57Who Should Care
- 12:02Can I Try It Without Upgrading
- 13:07Buildpack Groups
related talks
17mComing Soon to a Cloud Near You: Multiple Buildpack Support
24mBringing Cloud Native Buildpacks to Cloud Foundry
28mDelivering Heterogeneous Architectures
25mBoost Developer Productivity with Buildpacks
06mSponsored Keynote: Streamlining Your Application Builds with Cloud Native Buildpacks
35mIntro: Cloud Native Buildpacks
19mWhat It Takes to Make and Maintain a Buildpack and Stacks
48mIntro to Cloud Native Buildpacks