<#22558 Could you add `experimental_wrap_as_docker...
# github-notifications
c
#22558 Could you add `experimental_wrap_as_dockerfile`? Issue created by kilogram In order to improve CI (and local) build times, we've taken to splitting our pexes into deps/srcs and COPY/RUN ... --compile in different stages. However, the RUN appears to bust the cache -- likely because I need to specify a few more options:
RUN --mount=type=cache,target=/tmp/pex-cache,sharing=locked ...
I'm hoping to wrap all this up into a few macros or some kind of assistance so every time a team member adds a new image we don't have to go through the back-and-forth of discovering poor build times and fixing them. I tried using
adhoc_tool
to inject the commands, but no matter how I spell the dependencies or sources, I can't get it to accept the generated Dockerfile. I think the simplest thing (although I don't understand the finer points of pants backends) might be to add an
experimental_wrap_as_dockerfile
target. I see there's some prior discussion, but as far as I can find there's not been a resolution: • #17926 • #17877 • #13360 Thank you! Kevin pantsbuild/pants