You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recent issues with jib like spring-devtools and spring-boot-compose made me realize we need to move to Cloud Native Buildpacks.
I’ve implemented #27348 which switches CI to Buildpacks.
But made realize there is no way to support both due to healthcheck changes. Unless we customize jib to add healthcheck matching Buildpacks one.
Pros:
official Spring Boot support
out of the box arm64 support (without custom script)
features like CDS
no spring devtools workaround
no spring boot compose workaround
cons:
slower
Spring Boot only
And we do have jib instructions harcoded everywhere like deployment generators.
Migration consists in:
move npm scripts from postInstall to preparing application.
templates should read from npm scripts instead of hardcoded.
keep jib generator for micronaut support
maybe allow existing applications to keep jib?
Motivation for or Use Case
Related issues or PR
Checking this box is mandatory (this is just to show you read everything)
The text was updated successfully, but these errors were encountered:
Overview of the feature request
We use jib for docker support, would be nice to move to Cloud Native Buildpacks.
There a discussion in #26527
Recent issues with jib like spring-devtools and spring-boot-compose made me realize we need to move to Cloud Native Buildpacks.
I’ve implemented #27348 which switches CI to Buildpacks.
But made realize there is no way to support both due to healthcheck changes. Unless we customize jib to add healthcheck matching Buildpacks one.
Pros:
cons:
And we do have jib instructions harcoded everywhere like deployment generators.
Migration consists in:
Motivation for or Use Case
Related issues or PR
The text was updated successfully, but these errors were encountered: