tree a8b852486e5f59c2b5ca6e514c3536dea78b0889
parent adc80a301d8f144c8e5ac29fe377e7423417baee
author scentini <rosica@google.com> 1657890734 +0000
committer GitHub <noreply@github.com> 1657890734 +0000
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJi0WeuCRBK7hj4Ov3rIwAA2V0IAK8m1tZgTvGdca7w02fWNrfR
 DuG+sk2d1lawOKncLTbjcFNizLQSbOwe6BEevQ6xTx8itkEGIv4ojanh2Zjgggdm
 YRaViAYHt3B12jez3it1MJ8CDclPhq+FCbczyCUmO3kQ0+lqdc2ht6B87IPoCXrh
 DTR+xcsnbi+u8ldJdyBTuRnKea1j9JlTWaHYS7TXrhvsMH1RwdmYvn8NspMqzhMF
 u2XGP/vlaRvpiiU2RJqZrQIybnX/OHZK2GFNT2CU2R0Y//Xqm845hpvmonRZhAvq
 QSlfVLRqmwqcj8w918MknjflQCn3RIlpizgrLSU0pWmOx53yLL9mdPlQCVVwpUg=
 =YGm3
 -----END PGP SIGNATURE-----
 

Stamp only binaries by default (#1452)

Currently we pass `bazel-out/volatile-status.txt` to all the `Rustc` actions, which is bad for remote caching with `--stamp`enabled.

This PR makes only `rust_binary` be affected by the `--stamp` flag by default. The rest of the rust rules have `stamp = 0` as a default. Should you want to force stamp you can set `stamp = 1`. If you want to make your target stamp behavior depend on the `--stamp` command line flag, use `stamp = -1`.

Additionally, this PR makes `rules_rust` also use the stable keys for stamping, by passing `bazel-out/stable-status.txt` to the relevant `Rustc` actions when stamping is enabled. This makes `rules_rust` adhere to the contract described here: https://docs.bazel.build/versions/main/user-manual.html#flag--workspace_status_command