Brandon Schurman

Hi @shepherdjerred - I'm trying to narrow it down to a minimal example that reproduces it. This is what I have tried: `./Earthfile` ```earthly VERSION 0.6 dev.login: FROM alpine WORKDIR...

Hi @shepherdjerred , apologies for not seeing your follow-up message from a little while ago. Appreciate the thorough test script and logs you attached. I'll take a closer look into...

In your previous example, you have a target like this: ```earthly create: IF --no-cache ! [ -e "/root/artifact" ] RUN --no-cache echo $(date) > /root/artifact SAVE ARTIFACT /root/artifact /artifact AS...

And in your most recent example, are you expecting that since `+login` performs a `COPY` from `+dev.login`, that the `cache` would be outputted locally? That might be a common point...

Yeah, we use AWS quite a bit internally in Earthfiles here as well, and getting the auth setup right can be tricky. We actually ended up leveraging our own [Cloud...

I imagine this would be straight forward to implement, as we would leverage a lot of the infrastructure we already have for `ARG`

The contents in `CACHE` are mounted in buildkit as a cache thing (i.e. `llb.AsPersistentCacheDir`) and the `--no-cache` flag translates to a buildkit option `llb.IgnoreCache` - seems to me that this...

Updated to describe persistent cache without `--persist` flag (i.e. cache always persists, there's no need to use a flag). Also moved Phase II implementation into a separate issue: https://github.com/earthly/earthly/issues/1540 since...

Hi @chandraaditya , your setup in Github Actions looks good to me. The `--remote-cache` feature can have an expensive network cost, but I think that 20min export does seem a...

Thanks for sharing those details @chandraaditya. It does seem surprising to me that you would be CPU bound on a cache export for 20-30 mins. I'm not really sure why...