)]}'
{
  "commit": "3dd65a7cac20fc75f4f0da5ecf612a4766d90233",
  "tree": "7c8bccafbf5ce9cd46b89e370de82c1601b77156",
  "parents": [
    "00bf4549a2b189a19b45db894f875714ee49f1f1"
  ],
  "author": {
    "name": "Roger Luethi",
    "email": "roger@opennetworking.org",
    "time": "Wed Sep 20 13:10:29 2023 +0200"
  },
  "committer": {
    "name": "Roger Luethi",
    "email": "roger@opennetworking.org",
    "time": "Wed Sep 27 07:09:30 2023 +0200"
  },
  "message": "Abort if voltctl cannot find etcd\n\nThe voltctl commands we used to set log levels return only a rather\nunhelpful error message (\"context deadline exceeded\") if voltctl\nis unable to connect to etcd. The exit status in that case is 0,\nwrongly indicating success.\n\nThis happens quite easily if kubectl was configured to forward etcd to\na port other than the one expected by voltctl.\n\nUsing \"voltctl log level list\" as we do with this change has two effects\nif voltctl cannot find etcd. First, it exits with status 1 which should\nabort the pipeline, alerting the user to a configuration problem. Second,\nit prints a more helpful error message:\n\n  Is ETCD available at localhost:2379?\n\nSigned-off-by: Roger Luethi \u003croger.luethi@bisdn.de\u003e\nChange-Id: I7c2b0fdd8a2028c4b85b1a9b81c35dd194de99ca\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "5a14eaba5edfed8e68e7ada464d8e818c07def8c",
      "old_mode": 33188,
      "old_path": "jjb/pipeline/voltha/voltha-dt-physical-functional-tests.groovy",
      "new_id": "69fbced46117c0d413a5965d4f9efab5c2bd9c83",
      "new_mode": 33188,
      "new_path": "jjb/pipeline/voltha/voltha-dt-physical-functional-tests.groovy"
    }
  ]
}