{"push_id":1218853680,"size":1,"distinct_size":1,"ref":"refs/heads/skuznets/enforce-flake-id","head":"90adf75678d3ca9f17d755a840f832a17e7a592a","before":"484cc57c9183f4cc3bb24fa822c447a3c2c1b083","commits":[{"sha":"90adf75678d3ca9f17d755a840f832a17e7a592a","author":{"name":"Steve Kuznetsov","email":"590a2dd5117f7a12a3220171b278818cf486992b@redhat.com"},"message":"Implemented failed job explanation logic\n\nIn order to ensure that flaky tests cannot be easily\nignored by GitHub contributors that have the power\nto re-trigger Jenkins jobs, this new logic forbids a\njob from being re-triggered unless:\n - new code is pushed to update the pull request's\n   base branch from the version we used to run the\n   failed tests\n - a trusted user posts a comment linking together\n   the failed job's URL and the URL of valid GitHub\n   issues with labels identifiying them as test\n   flakes\n - an administrator re-triggers the job, which will\n   override any flake identification logic\n\nIf no flake identification configuration is done in\nthe JSON properties file, the legacy behavior is\nunchaged and the job will be re-triggered always.\n\nSigned-off-by: Steve Kuznetsov <skuznets@redhat.com>","distinct":true,"url":"https://api.github.com/repos/stevekuznetsov/test-pull-requests/commits/90adf75678d3ca9f17d755a840f832a17e7a592a"}]}
{"actor":{"display_login":"stevekuznetsov"}}