)]}'
{
  "commit": "9730f0bcd12fc5640fa68240b2fa5d21c3154c75",
  "tree": "2d4b5059b7ece251fb00ebf28cf4b7ef91d27322",
  "parents": [
    "e9a5dcb2f2eef825a0c7d053d7738900804dcd95"
  ],
  "author": {
    "name": "Thomas Draebing",
    "email": "thomas.draebing@sap.com",
    "time": "Thu Oct 10 14:34:12 2019 +0200"
  },
  "committer": {
    "name": "Thomas Draebing",
    "email": "thomas.draebing@sap.com",
    "time": "Tue Oct 15 15:03:23 2019 +0200"
  },
  "message": "Add Jenkinsfile for verification pipeline\n\nSo far the job for verifying changes in the `gerrit`-project was managed\nin the repository of the CI itself. These jobs were still using the by\nnow deprecated workflow type.\n\nThis change adds a Jenkinsfile to this project, which describes the build\nand test workflow to be executed by the CI. The job will be executed by a\nmultibranch pipeline in the CI.\n\nNote, that the job described in the Jenkinsfile for now just starts\nother jobs that will verify and check the code style of the change as it\nwas done so far in the `Gerrit-verifier-change`-job. It is planned to\nchange that in the future.\n\nNotable changes to the `Gerrit-verifier-change`-job are:\n\n- The job will not check on which branch it runs. The Jenkinsfiles present\n  in the different branches will have to contain the branch-specific\n  code.\n- In pipelines Jenkins is very strict in which methods are allowed to be\n  executed, since code can easily be added to a Jenkinsfile, which could\n  execute malicious commands on the CI. To avoid to have to whitelist such\n  methods in general, the code was adapted to only use allowed methods.\n- The job is now triggered by the `verifier-trigger`-job in the CI.\n\nChange-Id: I4d9ac3ebfd342243c6b7bf36186567e1b5175a4f\n",
  "tree_diff": [
    {
      "type": "add",
      "old_id": "0000000000000000000000000000000000000000",
      "old_mode": 0,
      "old_path": "/dev/null",
      "new_id": "bbd3c6016dfcc3c712fff566c6c8cc9134260550",
      "new_mode": 33188,
      "new_path": "Jenkinsfile"
    }
  ]
}