{"push_id":1279045454,"size":1,"distinct_size":1,"ref":"refs/heads/check-ghprb-actual-commit","head":"4d671bd7ba0644a820b6613512b89ba68c8aee29","before":"42d70b1daea9e6a743bd1ed39e7e37f0990cc6eb","commits":[{"sha":"4d671bd7ba0644a820b6613512b89ba68c8aee29","author":{"name":"Vaughn Dice","email":"e7d45f19bd6e2c924f3706f1135056a85d9e0cba@deis.com"},"message":"fix(bash/scripts/get_actual_commit.sh): inspect ghprbActualCommit\n\nWe'd previously tried not to rely on the environment for getting actual PR commits\n(specifically depending on the `ghprbActualCommit` env var provided by the GitHub Pull Request Builder Plugin)\nand instead invoked the `git` cli and/or curled the GitHub API directly, as a general practice\nof reducing dependencies on plugin code as well as increasing portability between jobs defined in DSL here\nand in Jenkinsfile logic, etc.\n\nBlah, blah, blah, anyways, since we _are_ still using the ghprb plugin, and we've seen [issues](https://github.com/deis/jenkins-jobs/issues/227)\nwith solely relying on the GitHub API, this change brings back logic to defer to the `ghprbActualCommit`\nenv var, when present, as the PR commit for building artifacts and updating statuses. (We'll still curl the api as a backup if not present.)","distinct":true,"url":"https://api.github.com/repos/vdice/jenkins-jobs/commits/4d671bd7ba0644a820b6613512b89ba68c8aee29"}]}
{"actor":{"display_login":"vdice"}}