Wil Gieseler

Hmmm... I replaced the build script with ``` Write-Output "Exit 1" Exit 1 Write-Output "THIS IS AN IMPOSSIBLE LINE" ``` And it properly exits and continues to the next step...

Narrowed it to ``` & "c:\steps\build.ps1" ``` in entrypoint.ps1 causing the hang. so something that happens in the build script is preventing exit. perhaps a process started there somehow never...

Actually, it's worse. It seems nondeterministic potentially.

I can't say it was quick for me to figure it out, but it looks like removing this line fixes the issue: ``` # Register the Visual Studio installation so...

I forked it to allow me to just pass memory and cpu count vars, since I could not figure out how to change the defaults. https://github.com/wilg/unity-builder

What's the latest on this situation. This problem just occurred to me so I'm wondering what the state of the art is? Perhaps strategies used by shipped Inkle games have...

I'm using Unity 2018.2.18f1. I'll check the other things in a bit!

Looks like it was the first problem, it wasn't saving the checkbox properly. I quit Unity and restarted it, and it was unchecked. I checked it again and it did...

Actually, I think a problem that's happening here is that when you click "Auto-Generate Version" it does not serialize `buildCounter` or `lastGeneratedVersion` into `UnityBuildSettings.asset`, so it's easy for the version...

dup of https://github.com/rubocop/rubocop-rails/issues/541?