Could someone please enlighten me about the lmdb store? In the docs there's a fragment about lmdb: > This has to be invalidated on any file that can affect any process, e.g.,

hashFiles('**/*')

on GitHub Actions. So this leads me to believe I can't cache it in Gitlab CI. However, using local lmdb cache on my laptop appears to be working fine and not sure if any invalidation occurs at all. I don't understand why this wouldn't work the same way in CI.

I think that specific bit is somewhat specific to GitHub's widely used action cache which is less "regular files" and more "magic thing with rate limits". Somewhat related discussion in https://github.com/pantsbuild/pants/issues/20133 Disclaimer: I have minimal experience with GitHub Actions. Using GitLabs' simple "just a zipfile" cache, I believe in theory you could cache the lmdb store. I think that would work okay. In practice if you are using GitLab and self hosted runners and S3, you are 90% of the way to configuring a remote cache.

Thanks for explanation!