{"push_id":2664319729,"size":1,"distinct_size":1,"ref":"refs/heads/trunk","head":"dd87bb234bce376155dbddf278f182b7ac075748","before":"1a5caadac4e8961f29c1b8664152afec70a63eb0","commits":[{"sha":"dd87bb234bce376155dbddf278f182b7ac075748","author":{"name":"Rob Goodridge","email":"66557ac4ee94d0e7c036a5759f058124be8ed917@lansa.com.au"},"message":"160274 Powershell remote error handling architecture revamped. See below...\n\n\t1. Exception in remote is percolated back via $LASTERRORCODE\n\t2.\nWe must know of ANY ERROR so, WRITE-ERROR ALWAYS generates an EXCEPTION\nJust throw <message> instead of using Write-Error\n\t3.\nOutput maybe lost in remote if the top most script throws\n\t4.\nTop-level script catch block outputs exception and stack trace to aid debugging\n\t5.\nScripts must use Write-Host so that its always output to the console\n\t6.\nScripts may not execute correctly in re-used sessions\n\t7.\nImplement a system modal message box so you know immediately the script finishes or requires input","distinct":true,"url":"https://api.github.com/repos/robe070/cookbooks/commits/dd87bb234bce376155dbddf278f182b7ac075748"}]}
{"actor":{"display_login":"robe070"}}