How does Pants-core go about testing all its backe...
# plugins
a
How does Pants-core go about testing all its backends for things that it has no way of installing (i.e. docker??) I can't imagine it's particularly easy to have everything set up in one environment so
pants test
can run all docker, python, and whatever else it supports.
context: Trying to write tests for rules that calls pants-unmanageable binaries
b
You'd be surprised at what is on the default GitHub runner image: https://github.com/actions/runner-images/blob/main/images/linux/Ubuntu2004-Readme.md
a
no micropython tho 😞
b
Oh dang I never looked into micropython before, looks really cool
w
in general, we try to bias toward automatically installing tools… there are some exceptions, but mostly for legacy reasons. for example: we find a locally installed
go
distribution because we didn’t use to have support for immutable and append only caches
but JVMs, pyoxidizer, etc, etc are fetched instead.