Alex Couture-Beil

One thing that's off with this PR is the final output shows some duplicate `BUILD +test-executor` output at the end of the build. Here's a complete example: consider the Earthfile:...

Thanks for the report. It looks like your code example defines `ARG ID`, however never uses it, and instead passes `--cache-id=test`. If it's changed to `--cache-id=$ID`, I I noticed the...

I should mention that when the `cache-id` has the same value, it's intentional that `WITH DOCKER` does not run in parallel -- this is to avoid corrupting docker's data-root.

We still perform a pull each time to make sure the image hasn't changed; however the underlying image layers are cached. We chose to do this deliberately as a way...

> With "having the process repeatable" you mean across Earthly pipeline executions with caching right? Yes. This also includes cases where you run a target, edit your Earthfile (e.g. changing...

Great find @jrodrigv; I have a potential implementation to support this under #4138; however there's some duplicate output that's causing some issues that needs to be addressed before it's ready...

> I think Renovate could achieve this with custom matchers: https://docs.renovatebot.com/modules/manager/regex/ It most definitely can; we use it in fact for keeping our `earthly/dind:..` tags up to date: https://github.com/earthly/earthly/blob/488d8ccae92e4847e5754d87d5b428c29fee1fed/.github/renovate.json5#L99

Have you looked into the `IMPORT` command? You can have a base target like: ``` VERSION 0.8 common-alpine-target: FROM alpine:3.18 RUN echo "this should be available everywhere" > /common-data ```...

unfortunately `IMPORT` doesn't allow you to import any `ARG` or `LET` definitions; but I could see this being a nice addition (especially if we add a `CONST` one day #1863)

it's also possible to inherit a `ENV` value from a different target (where as `ARG` values are not inherited)