)]}'
{
  "commit": "bf79cd73eb88db2c8cf752e975343051c97bfd54",
  "tree": "d1fbbfb567df8ccfed05c6cf7ffda63f3139468e",
  "parents": [
    "1a134ba6d492c928e2664cfdab20468538fb8442"
  ],
  "author": {
    "name": "Thomas Draebing",
    "email": "thomas.draebing@sap.com",
    "time": "Fri Nov 15 12:36:21 2019 +0100"
  },
  "committer": {
    "name": "Thomas Dräbing",
    "email": "thomas.draebing@sap.com",
    "time": "Sat Nov 16 05:58:18 2019 +0000"
  },
  "message": "Fix reporting for flaky builds in Jenkinsfile\n\nThe verification pipeline was not properly reporting the results of\nbuilds that were suspect to being flaky. This happened, because the\nbuild did not save the results in a variable, if the propagate option\nwas used, which had to be done for the pipeline plugin\u0027s retry command\nto work.\n\nInstead of using the retry-command provided by the pipeline plugin,\nthe Jenkinsfile implements this behaviour manually.\n\nBug: Issue 11927\nChange-Id: I419a20f69cabc4c54d7f57fd04ad354563eafd71\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "ebf2136b4b46375dad7785388cc7afacbc422b35",
      "old_mode": 33188,
      "old_path": "Jenkinsfile",
      "new_id": "e09b0f0befca11f96ba525c3b56149fe4306d456",
      "new_mode": 33188,
      "new_path": "Jenkinsfile"
    }
  ]
}