GitHub Discussion re REAPI v3 and how it might imp...
# development
f
GitHub Discussion re REAPI v3 and how it might impact Pants. (There is no REPAI v3 yet but there is a position paper from build tools community on what direction it should take.) See https://github.com/pantsbuild/pants/discussions/21411.
Ed from BuildBarn had forwarded the doc to me in the Spring. Finally got around to digging through old emails ...
h
@fast-nail-55400 Do you think this document is the right place to suggest a feature for splitting the cache entries for a process by its input files? E.g., we actually run
linter a.py b.py c.py
but we cache as-if we ran each of
linter a.py
,
linter b.py
,
linter c.py
separately. Of course this would require the author to be able to guarantee that those are acceptably equivalent action sets.
f
I'm hesitant to propose it for the REAPI document because it would require REAPI servers to know how to add extra Action Cache entries for specific process run. Pants can do that by simply writing the Action Cache entries itself once the applicable remote execution ends.
We could propose some generic means of specifying what Action Cache entries to write, but we would likely get pushback that Pants itself can contain that knowledge and just write the additional Action Cache entries.