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
Since Platform API 0.3, CNB builders support a creator lifecycle. This lifecycle executes all other lifecycle phases (detector, analyzer, restorer, builder, exporter) in the proper order.
Using the creator has a few benefits for Spring Boot:
All lifecycle phases are run in the same container instead of each phase being run in its own container. This has shown to reduce image build time by ~6 seconds.
Phase orchestration is delegated to the creator, insulating Boot from future orchestration changes like phase ordering which has happened between lifecycle versions.
Builder invocation code can be simplified considerably.
Boot could continue to support conditionally running discrete phases to retain compatibility with Platform API 0.2 builders, or only support API 0.3 or greater and only run the single creator lifecycle. Dropping support for API 0.2 would give the greatest benefit in code simplification.
The text was updated successfully, but these errors were encountered:
Prior to this commit, the build tool plugins set the environment
variable BP_JAVA_VERSION when invoking the CNB builder to set the
version of the JDK/JRE that the builder should use in the created
image.
With CNB API 0.3, the convention changed the name of this environment
variable to BP_JVM_VERSION. This commit updates the build tool
plugins to match the newer convention.
See spring-projectsgh-21273
Since Platform API 0.3, CNB builders support a
creator
lifecycle. This lifecycle executes all other lifecycle phases (detector
,analyzer
,restorer
,builder
,exporter
) in the proper order.Using the
creator
has a few benefits for Spring Boot:creator
, insulating Boot from future orchestration changes like phase ordering which has happened between lifecycle versions.Boot could continue to support conditionally running discrete phases to retain compatibility with Platform API 0.2 builders, or only support API 0.3 or greater and only run the single
creator
lifecycle. Dropping support for API 0.2 would give the greatest benefit in code simplification.The text was updated successfully, but these errors were encountered: