[WIP] feat(unity): add auto discoverability, testing, and publishing for unity3d projects

[sjk07]

Condo can now discover, test, and publish Unity3d projects.

Some caveats:
unity.condo file must be at the root of your project. Still figuring out a good way to auto-discover the root level of a unity3d project

UNITY_PATH must be set, this is because unity does not get set on the path and they use relative pathing on the executable...

BUILD_TARGET will default to WebGL build if not specified. WebGL builds can also get built into a docker container on publish!

Publish When publishing had to add the -noUpm flag to disable package manager. Not sure how this effects final builds.
Also there is a hard requirement for a custom build script in your project, -executeMethod Build.PerformBuild, Will have to find a way to remove this requirement or publish the code somewhere.

Will have to add support for licensing and user/pass/key

Output with AllowPublish set to true:
condo -- /t:publish

         ----- Total AssetImport time: 0.459228s, AssetImport time: 0.179834s, Asset hashing: 0.000000s [0 B, 0.000000 mb/s]

         Refresh: detecting if any assets need to be imported or removed ...
         Refresh: elapses 0.005950 seconds (Nothing changed)
         Refresh completed in 0.006006 seconds.
         Cleanup mono
         debugger-agent: Unable to listen on 23
         Exiting batchmode successfully now!
       CreateRelease:
         Saved the conventional changelog: CHANGELOG.md...
       DockerBuild:
         docker build --label test --tag test:0.1.0-alpha-00340-0427 -f "/Users/scott/projects/nightly/games/test/Dockerfile" "/Users/scott/projects/nightly/games/test"
         Sending build context to Docker daemon  325.6MB

         Step 1/4 : FROM nginx:alpine
          ---> 63356c558c79
         Step 2/4 : ARG SOURCE
          ---> Using cache
          ---> 68a76b842d8c
         Step 3/4 : COPY ${SOURCE:-artifacts/publish/webgl} /usr/share/nginx/html
          ---> e52af7bee569
         Step 4/4 : LABEL test=
          ---> Running in c9c7a272c55e
         Removing intermediate container c9c7a272c55e
          ---> 53f03e3c854d
         Successfully built 53f03e3c854d
         Successfully tagged test:0.1.0-alpha-00340-0427
       DockerTag:
         docker tag test:0.1.0-alpha-00340-0427 test:0.1.0-alpha-00340-0427
     1>Done Building Project "/Users/scott/projects/nightly/games/test/condo.build" (publish target(s)).

Build succeeded.

closes #243

[dmccaffery]

I don’t know enough about unity to know whether or not all the options on the build and test phases make sense; so I leave it to you... just wondering if these are so common that they should always be specified for everyone using condo for unity.

[dmccaffery]

Is the nographics switch common? Should it be an option?

[dmccaffery]

Same for custom build target?

[dmccaffery]

Same for additional flags, like options... should these be defaulted but still overridable ala DOTNET_TEST_OPTIONS, etc?

[sjk07]

-quit -batchmode -nographics are all defined in the unity docs for running a CI build. If they are not set then unity will not close the process when complete, and open a GUI interface

Still playing around with customBuildTarget. to run unity headless you need to have an entry point file.

adding the additional flags is a good idea

[sjk07]

docs: https://docs.unity3d.com/Manual/CommandLineArguments.html

[sjk07]

Will leave this PR as WIP until I get a few unity builds running on CI and test actual outputs.

[sjk07]

no progress, closing for now