Feature request
As a software developer,
I want to use a SDKMAN CLI image as a base for a CI job,
in order to avoid managing different images for each JDK version
Currently, you need to update the CI runners' images if you switch your application's Java version (you have to deal with Java version in two places).
If a SDKMAN image is published in hub.docker.com, you would only need to handle the JDK version on your repository .sdkmanrc file. Thus making easier the change of java versions, and the runner images management (as developers won't require CI jobs to be changed).
It will also assist you beyond that as you could also install other candidates (as for example Kotlin) without creating another CI image.
Finally, it would be great to also allow to change the candidates directory in order to make caching possible on most CI platforms.
The steps to make this possible would be:
- Create a Dockerfile with the CLI installed
- Build the image on GitHub actions on PRs
- Push the image to hub.docker.com on each release
Feature request
As a software developer,
I want to use a SDKMAN CLI image as a base for a CI job,
in order to avoid managing different images for each JDK version
Currently, you need to update the CI runners' images if you switch your application's Java version (you have to deal with Java version in two places).
If a SDKMAN image is published in hub.docker.com, you would only need to handle the JDK version on your repository
.sdkmanrcfile. Thus making easier the change of java versions, and the runner images management (as developers won't require CI jobs to be changed).It will also assist you beyond that as you could also install other candidates (as for example Kotlin) without creating another CI image.
Finally, it would be great to also allow to change the candidates directory in order to make caching possible on most CI platforms.
The steps to make this possible would be: