Tom Prince c520218cec 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.		2020-04-13 16:50:13 -06:00
..
build.go	Don't generate cache key, if not caching builds.	2020-04-13 16:50:13 -06:00
build_test.go	Merge pull request #1085 from tejal29/rm_buildargs_from_cache_key	2020-03-17 16:02:59 -07:00
composite_cache.go	fix resolve link for dirs with trailing /	2020-03-06 09:38:00 -08:00
composite_cache_test.go	update build and composite cache tests	2020-01-23 15:37:38 -08:00
fakes.go	remove build args from composite key and replace all build args before adding command to the cache	2020-02-28 01:51:31 -08:00
push.go	Create constant for Docker conf location	2020-03-21 16:45:04 -07:00
push_test.go	Test: Remove DockerConf after CheckPushPermission	2020-03-23 10:51:09 -07:00