Experiences in Adopting Paketo in Shipwright and IBM Cloud Cod...
summary
Adopts Paketo buildpacks inside Shipwright and IBM Cloud Code Engine, implementing a Shipwright Paketo build strategy that calls the lifecycle binaries one phase at a time instead of running pack. Productizes builds so Code Engine CLI creates a Knative app and a Shipwright build that produces and pushes images; it works but required adding env var support, contributing fixes (multiple Java file support, Node build script), adding end-to-end regression tests, and noting missing features like bindings support and export to OCI directory for offline scanning.
AI-written summary · about
chapters (14)
- 0:00Introduction and speakers
- 1:03What are Paketo build packs
- 3:50What is IBM Cloud Code Engine
- 4:11What is Shipwright
- 5:17Building blocks in Shipwright
- 6:24Paketo in Shipwright workflow
- 8:33Missing features in Shipwright
- 11:43Challenges adopting Paketo
- 13:26Pack vs direct lifecycle phases
- 14:51Exporting to filesystem for security
- 17:01User expectations with build packs
- 19:48Support statements for build packs
- 21:30Thank you and community acknowledgment
- 22:13Q&A session
related talks
33mDeploy & update Jakarta EE & MicroProfile Applications with Paketo
07mPaketo Buildpacks: the Best Way to Build OCI Images?
47mUnderstanding Buildpacks: A Deep Dive Into Their Functionality
03mPaketo Working Group Updates
25mBoost Developer Productivity with Buildpacks
01h 04mDon't Put All Your Eggs in One Buildpack
27m50 Ways To Build Containers?
45mKeynote: