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
KAS_BUILD_DIR is not really a project setting, it's a local decision. Or why should all users of your configs split the build dirs like you suggest?
But even if we wanted to introduce a configurable default value to the config, that would not work across kas-container. It needs to know this value but has no parser for configs with all their includes and overrides (except for very simplistic top-level evaluations).
I think I understand the problem, I'll investigate why my scarthgap builds can't co-exist with my kirkstone builds and/or change the TMPDIR and cache directories maybe...
My use case here is that I have a kirkstone.yaml and a scarthgap.yaml and I would like them to have completely separate build directories.
Is there a way to set this up so that I don't need to manage environment variables via another wrapper script?
If not, can this setting be exposed to the yaml config?
The text was updated successfully, but these errors were encountered: