[Unity] Run tests on CI

[geragray]

We need to be building the Unity tests on CI for all platforms and all scripting backends. Since Unity cannot cross-compile with IL2CPP, we'll need to build on Linux, macOS, and Windows separately.

Rough breakdown of the tasks is:

• [x] ~Prepare a cross-platform Github action for building the Unity test runner~
  • [x] Needs to run editor in -batchmode
  • [x] Needs to obtain a floating license and release it once done
• [x] Provision self-hosted Linux instance for building for Linux and Android.
  • [x] Needs the Unity editor installed
  • [x] Needs workloads for Linux (Mono and IL2CPP) and Android
  • [x] Needs to be able to connect to the licensing server
• [ ] @bwachter Provision self-hosted macOS instance for building for macOS and iOS
  • [ ] Needs the Unity editor installed
  • [ ] Needs workloads for macOS (Mono and IL2CPP) and iOS
  • [ ] Needs to be able to connect to the licensing server
• [ ] Provision self-hosted Windows instance for building for Windows and UWP
  • [x] Needs the Unity editor installed
  • [x] Needs workloads for Windows
  • [x] Needs to be able to connect to the licensing server
  • [x] (@bwachter) Update unity-editor script to retry the build if we hit a license limit
  • [x] (@bwachter) Update unity-editor to log output from the returnlicense call
  • [ ] (@nirinchev) Test IL2CPP scripting backend
  • [x] (@bwachter) Install win10 sdk: Windows 10 SDK is not installed. You can install from here: https://developer.microsoft.com/en-us/windows/downloads/windows-10-sdk/.
  • [x] (@bwachter) unity-editor should return an error code if the build fails.

[nirinchev]

Point of contact from Realm: @nirinchev and @LaPeste

[bwachter]

TL;DR for mac: I have a VM with OS-X/intel capable of doing Unity builds with a fixed seat license. Can be used to get mac tests running while I work on getting it to cooperate with the license server as soon as I get a github token to register the runner there.

Unity on OS-X has quite a few issues, and mostly does error handling by not logging anything and not terminating - so a lot of hung processes without obvious reason. Adding to that is that they're wildly jumping between putting data in the users home and system wide location for the licensing client - not all of them are writeable on a default installation, and not in all instances do they handle write errors gracefully. On top of that parts of the license validation seem to call APIs which only work if the user running the license service also has an active desktop session - so currently unity on mac is running as a user logged into the desktop, with the ability to gain elevated privileges, which is not quite ideal.

I've also observed some freezes which seemed to have been due to powershell - so to rule that out as problem currently the unity-editor wrapper on mac is just exec /Applications/Unity/Unity.app/Contents/MacOS/Unity $@

I've cloned the VM with the working builds to one of our servers, so it can be registered as github worker, and am now working on a copy of it to get the interaction with the license server working.

[bmunkholm]

Nikola will look into this issue next week.

[bmunkholm]

No progress so far for Nikola on MacOS tests. Andrea will write wiki on how to simulate CI run locally.