)]}'
{
  "commit": "72926b5d0b947b00d4e658710fe2d5ac76b0fc44",
  "tree": "52d5f893f6a4b3cf25e08a2aa92e1664157b7818",
  "parents": [
    "80995a3fcbab16c921203b0b283335aadd221e5a"
  ],
  "author": {
    "name": "Salma Samy",
    "email": "16399431+SalmaSamy@users.noreply.github.com",
    "time": "Wed Jul 01 16:54:29 2026 +0200"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Wed Jul 01 16:54:29 2026 +0200"
  },
  "message": "Add docker group to Buildkite docker plugin config (#2699)\n\nFix [this\nerror](https://buildkite.com/bazel/bazel-bazel-github-presubmit/builds/34290#019f1cb3-0d36-48f5-8f69-f4bba4be27cc/L906),\ncaused by the [security hardening\ncommit](https://github.com/bazelbuild/continuous-integration/commit/c1c1db8dbd0cff3b8d00d79530329878082d4f89),\nwhich restricted the host\u0027s Docker socket permissions to 0660 (allowing\naccess only to root and members of the docker group).\n\nBecause the Buildkite agent runs CI build steps inside Docker containers\nunder a custom user ID, the containerized processes lacked permission to\ncommunicate with the host\u0027s hardened docker.sock. Adding \"docker\" group\nto our Buildkite Docker plugin configuration resolves this by granting\nthe containers the necessary group membership to access the socket and\nexecute Docker commands successfully.",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "bdb3e5ce41a9a1a5c901d6957f43c73a03935d76",
      "old_mode": 33261,
      "old_path": "buildkite/bazelci.py",
      "new_id": "c9945e95e7e4ad0dae43a5743defc6e650dc2393",
      "new_mode": 33261,
      "new_path": "buildkite/bazelci.py"
    }
  ]
}