aboutsummaryrefslogtreecommitdiffhomepage
path: root/site
diff options
context:
space:
mode:
authorGravatar Klaus Aehlig <aehlig@google.com>2018-07-23 02:22:20 -0700
committerGravatar Copybara-Service <copybara-piper@google.com>2018-07-23 02:23:16 -0700
commit49212c43c1aef61319d69760ca79151636988b68 (patch)
tree4bd061bad83b44cc955a6a858a4e1e5f86e1a0b7 /site
parent6b5df97308d5ce60e801f9872d6b354db5164fe6 (diff)
resolved file: include the hash of the output tree
When reporting about the repository rules that were called, also report a hash of the tree the rule generated. This allows, at least after the fact, to verify that a repository rule actually produced the correct code. Note that equality of the output hash is not a guarantee for reproducible builds, as certain properties of the output tree, in particular owner, are ignored. Still it is a good check to detect wrong use of a repository rule. Change-Id: Ic56509f8e0d0b4be9ce3335ade280f983fe77e6d PiperOrigin-RevId: 205631855
Diffstat (limited to 'site')
0 files changed, 0 insertions, 0 deletions