{"head":"d185d23d02e94e2e99283d6ff07c7fb582ead253","size":1,"push_id":44813108,"shas":[["d185d23d02e94e2e99283d6ff07c7fb582ead253","39182686bd4535e7c1d8594f38c45f0854afa1bd@wp.pl","Returning non-zero exit code on build failure is done in psake.cmd instead of in Invoke-Psake\n\nNow Invoke-Psake newer exits whole PowerShell process, so it is possible to run psake more than once in one build server run.\nAlso it fixes problem with random freezes on errors. They happened because psake tried to find out if it is called by windows service and used ParentProcessId,\nbut Windows is not Unix;), and this Id can point to terminated or completely different process, and such process can again point to first process, and it causes infinite loops.\n\nAlso formatting changes in psake.ps1, now is the same formatting style as in psake.psm1","whut"]],"ref":"refs/heads/private_exit"}