Don't generate cache key, if not caching builds.

The cache key generation does environment subsitution in places that running
the commands doesn't. This causes issues if a command uses complex shell
substitutions. The cache key is generated even if caching isn't enabled.

This disables the cache key generation if caching is not enabled. This doesn't
fix the underlying issue, but limits it to when the cache is being used.
This commit is contained in:
Tom Prince
2020-04-13 16:50:13 -06:00
parent 1978f1e08e
commit c520218cec
2 changed files with 20 additions and 14 deletions
@@ -0,0 +1,2 @@
FROM docker.io/library/busybox:latest@sha256:afe605d272837ce1732f390966166c2afff5391208ddd57de10942748694049d
RUN echo ${s%s}