)]}'
{
  "commit": "24664fdefc113a2fc28cfebf6d980a896f213e04",
  "tree": "1ee84353e4277387469ddde91237d96489d939f7",
  "parents": [
    "e3b8484730dace16b71d69c3164c39721e983318"
  ],
  "author": {
    "name": "Luca Milanesio",
    "email": "luca.milanesio@gmail.com",
    "time": "Sat Oct 03 12:36:21 2026 +0100"
  },
  "committer": {
    "name": "Luca Milanesio",
    "email": "luca.milanesio@gmail.com",
    "time": "Sat Oct 03 04:56:09 2026 -0700"
  },
  "message": "Workaround for allowing BuildBuddy fetch of the Docker build image\n\nAfter the upgrade of the on-prem BuildBuddy runner to\nenterprise-v2.312.0, the fetch of the container specified in Gerrit\u0027s\ntools/remote/BUILD under the platform\u0027s exec_properties container-image.\n\nSee the official BuildBuddy documentation on how to use credentials for\nfetching Docker images from GCR at [1].\n\n[1] https://www.buildbuddy.io/docs/rbe-platforms/\n\nChange-Id: I75db4ca8526cdcb6a85b8aacb9e350705a3ab9f4\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "d31d6fa5c37b47da2d38a679e9b51e0fb7bb8a90",
      "old_mode": 33188,
      "old_path": "jenkins/gerrit-bazel-build.sh",
      "new_id": "25ceb3e00498c7b69eef8901968313a9f7c6e1ac",
      "new_mode": 33188,
      "new_path": "jenkins/gerrit-bazel-build.sh"
    },
    {
      "type": "modify",
      "old_id": "c6846ea9485e148f68247da16a9754130c5dec8a",
      "old_mode": 33261,
      "old_path": "jenkins/gerrit-bazel-test.sh",
      "new_id": "3edfca949b62f37515f7b4e23c02de77f60cb153",
      "new_mode": 33261,
      "new_path": "jenkins/gerrit-bazel-test.sh"
    },
    {
      "type": "modify",
      "old_id": "4f3cc97a192167a212c05b699445ef5cb014a4d3",
      "old_mode": 33261,
      "old_path": "jenkins/gerrit-bazel-verifier-test.sh",
      "new_id": "38f3a257c778b8af920e4fdb497b36fb1bee99ed",
      "new_mode": 33261,
      "new_path": "jenkins/gerrit-bazel-verifier-test.sh"
    }
  ]
}