Better way to wait for build and check exit code

From here:

https://github.com/Dinomite-Studios/unity-azure-pipelines-tasks/blob/4a64eda5de819563cb17d3a4da7e1cfdc6a30d2d/Tasks/UnityBuild/UnityBuildV2/unity-build.ts#L83-L94

I suggest replacing it with a far simpler way:

start “Unity build” /wait “C:\Program Files\Unity\Editor\Unity.exe” -batchmode -buildTarget standalone -projectPath .\src\UnitProject -logfile editor.log -quit

The cmd.exe command start /wait will not exit until the process you started exits, and it propagates the exit code of that process back to the caller, allowing the Pipeline to fail with an error. Also, the -quit switch ensures that unity.exe exits when the build is done.

[milsoft]

@AArnott @FejZa consider wrapping the execution in a powershell job. Look at the documentation for Start-Job Get-Job and Wait-Job. You can also get status of things this way, and there are ways to dig deep to get child processes spawned by the jobs.

[FejZa]

Fixed in v2.7