On Wed, Dec 27, 2017 at 8:46 PM, Jonathan Nieder <jrnieder@xxxxxxxxx> wrote: > SZEDER Gábor wrote: > >> Travis CI creates that directory for us anyway, even when a previous >> cache doesn't exist for the current build job. >> >> In itself it doesn't hurt to try, of course, but the following patch >> will access the Travis CI cache much earlier in the build process, and >> then creating the cache directory this late might cause confusion. >> >> Signed-off-by: SZEDER Gábor <szeder.dev@xxxxxxxxx> >> --- >> ci/run-tests.sh | 1 - >> 1 file changed, 1 deletion(-) > > Is this behavior documented anywhere? > https://docs.travis-ci.com/user/caching#Arbitrary-directories doesn't > say anything about it. No, I'm afraid it isn't explicitly mentioned. I seem to remember an example implicitly relying on it, though, but can't find it anymore, so either misremembered or misunderstood one of the examples. OK, then I'll move this 'mkdir' to 'ci/lib-travisci.sh', to ensure that the cache directory exists in all build jobs. Gábor
