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
Description of the issue: It would be convenient to be able to set the base layer cache directory programatically, for example to set it to project.getGradle().getGradleUserHomeDir() to keep it together with other gradle caches if desired.
Expected behavior: Currently, it seems to only be possible to either say yes/no to project-level cache, or use the environment variable XDG_CACHE_HOME. It is often difficult to set an environment variable programatically or in a way that allows reproducible builds (e.g. applies to both CI and dev machines).
Environment: gradle-jib-plugin
The text was updated successfully, but these errors were encountered:
Hi @anuraaga , thanks for the suggestion! We'll consider adding this since it does enable better control over caches across multiple machines. However, one thing we do wish to avoid is to enable bad practices like placing full paths in a pom.xml where the full paths are specific to a single machine and not portable across machines.
Description of the issue: It would be convenient to be able to set the base layer cache directory programatically, for example to set it to
project.getGradle().getGradleUserHomeDir()
to keep it together with other gradle caches if desired.Expected behavior: Currently, it seems to only be possible to either say yes/no to project-level cache, or use the environment variable XDG_CACHE_HOME. It is often difficult to set an environment variable programatically or in a way that allows reproducible builds (e.g. applies to both CI and dev machines).
Environment: gradle-jib-plugin
The text was updated successfully, but these errors were encountered: