)]}'
{
  "commit": "b3db3dd202669bf8b7b1adcbfe4b5d6d55eebdde",
  "tree": "e60408555c39d01a650a3129aa5bb076dc1b16e9",
  "parents": [
    "fd387a4d25284b5111afbf251454f7cc6bf11eac"
  ],
  "author": {
    "name": "Geoffrey Martin-Noble",
    "email": "gcmn@google.com",
    "time": "Wed Aug 25 15:32:16 2021 -0700"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Wed Aug 25 15:32:16 2021 -0700"
  },
  "message": "Use RBE to cache TF build results (#6867)\n\nTF makes it a total PITA to build it with remote execution, but we *can*\r\nget a bunch of the benefits (and with much less configuration) with\r\nremote caching. This has actions executed locally but cached remotely.\r\n\r\nNote that we need to ensure that the machines reading and writing from\r\nthe cache are ~identical, so this should only be executed inside of a\r\ndocker container and the docker image digest is used as the cache key.\r\n\r\nNot really sure why I didn\u0027t think of this earlier.\r\n\r\nTested: observe that in the integrations build of the second commit\r\nhere, the Bazel part of the build took 30 seconds.",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "226e4fdd659d2dd1bcb2d1b5e7a9e3b96619203b",
      "old_mode": 33188,
      "old_path": "build_tools/bazel/iree.bazelrc",
      "new_id": "ec3ab83d8a19f1bfb01dc642ef8d63e0a53a0853",
      "new_mode": 33188,
      "new_path": "build_tools/bazel/iree.bazelrc"
    },
    {
      "type": "modify",
      "old_id": "5966d91c95b0322582b69dc41712bbe72e24b656",
      "old_mode": 33261,
      "old_path": "build_tools/kokoro/gcp_ubuntu/cmake-bazel/linux/x86-swiftshader/build.sh",
      "new_id": "d1869ac463dd0ce325d8fd9bb0d6689e40b302c6",
      "new_mode": 33261,
      "new_path": "build_tools/kokoro/gcp_ubuntu/cmake-bazel/linux/x86-swiftshader/build.sh"
    }
  ]
}