Unable to be used in CI

Question

Unable to be used in CI

juanca opened this issue 7 years ago · 3 comments

juanca commented 7 years ago

See original comment @
070af07#r26826081

Looks like there is some timestamp-fu that is not allowing the .cache-loader/ folder to be cached across VMs.

Answer 1 · 2018-01-13T00:00:55.000Z

I think I'm understanding why it doesn't work in CI:

When a CI container pulls in the codebase, each of those files gets an up-to-date modified time (mtime).

However, the .cache-loader files have stored an mtime of the last build.

Answer 2 · 2018-01-15T20:16:51.000Z

I'm closing this issue since it looks like this is done by design. I would be open to improving the caching mechanism. Let me know if y'all are also open to that idea.

Answer 3 · 2018-03-13T12:29:47.000Z

The fact that I can't use this loader in my CI is very disappointing. I could be using that to decrease build time from 5m to 30secs...