A native executable of the application deployed as a docker image to cloud run will improve cold startup time.
You have to first be able to generate a native executable successfully. For me, it fails with:
> Task :grails-forge-core:generateRockerTemplateSource
ANTLR Tool version 4.5.3 used for code generation does not match the current runtime version 4.8ANTLR Runtime version 4.5.3 used for parser> Task :grails-forge-core:compileJava
Note: Creating bean classes for 76 type elements
/Users/sdelamo/github/grails/grails-forge/grails-forge-core/src/main/java/org/grails/forge/util/IOFeatureUtil.java:52: error: reference to newFileSystem is ambiguous
final FileSystem zipFs = FileSystems.newFileSystem(Paths.get(URI.create(jarPath)), null);
^
both method newFileSystem(Path,ClassLoader) in FileSystems and method newFileSystem(Path,Map<String,?>) in FileSystems match
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
1 error
Once, you are able generate a native executable inside a docker image and run it locally and generate grails applications, you need to change the GitHub workflows as described in this commit:
A native executable of the application deployed as a docker image to cloud run will improve cold startup time.
You have to first be able to generate a native executable successfully. For me, it fails with:
Once, you are able generate a native executable inside a docker image and run it locally and generate grails applications, you need to change the GitHub workflows as described in this commit:
https://github.com/grails/grails-forge/commit/eb94e6a8c323482496304e2189590d18bab19434