Andreas Stenius

> `help-all` still only shows JSON for the currently active backends right? yes. EDIT: actually, it also includes info on _all_ backends, so you can see which are available, and...

Hi, thanks for reporting. Just to confirm, is the `output` field for your `docker_image` target using the default value of `{"type": "docker"}`? Also, please include the git sha of your...

> Git SHA is [7e15e5c](https://github.com/pantsbuild/pants/commit/7e15e5c3c2d3c0f0e944f697ae6a0c550249aad0) 👍🏽 > I am using the default value for type. ✅ > I am not using a multi-platform build afaik; I am using a multi-stage...

How do you stitch multiple `docker_image` targets into a single multi-stage build? Or, I guess it's not a multi-stage build in Docker terms, perhaps? (i.e. in Docker a multi-stage build...

OK, I'm not sure what's up with buildx here. Perhaps @riisi have more insights? Regarding what Pants does, it simply chains multiple docker builds, something ~eq. to: ``` docker build...

regarding a stable hash, see the `{pants.hash}` interpolation value from https://www.pantsbuild.org/docs/tagging-docker-images#string-interpolation-using-placeholder-values

We've been using this target with great success for over 2 years at Svenska Spel now.. it's time we upstream it ;)

For more advanced mirroring needs, you could derive a Pants macro along the lines of what we have done, that either uses this new mirror target, or merely constructs a...

Thanks Tom, that actually looks more clean. The thing I've posted here is driven by the use cases we needed to support internally, and I wanted a syntax that allowed...

> @fromfile should work for args and env vars too. you missed my point, that's still a "configuration" option, you commented on a target field type.