David Finol
David Finol
I'm not familiar with `-manualLicenseFile`, but the error is complaining about username/password, so maybe you need to add them to the activation command? ` -username "$UNITY_EMAIL" -password "$UNITY_PASSWORD" `
I think the simple solution may be to use the Unity Editor to open each scene in the build settings. If any lighting files are generated, the build would fail...
If we want to generate lighting in CI, we can call lightmapping.bake : https://docs.unity3d.com/ScriptReference/Lightmapping.Bake.html How would we check every material in every scene for lit shaders? Even if we are...
I think having an npm package could work well. What do you think, @webbertakken ?
> With the eyes on the future, perhaps making a monorepo (core) and using composite actions (our existing builder, test-runner, activate etc) to call its actions might be a good...
I like this second option of creating a SonarQube "target". I recently got SonarQube without using docker images, but it would be nice to have images for SonarQube, to avoid...
I'd be interested!
>This returns a zero exit code. The license is in fact activated and running unity again from the command line succeeds. Returning the license also succeeds. @st0nerhat This sounds like...
I'd recommend first doing the activation in one step, and then running the `-executeMethod` in a follow-up second step. That's the pattern that our GitHub Actions use, and I don't...
> Are most people here on linux? From what I've seen, most people are on Windows. You can do `base64` on Windows by using the git bash. > The folders...