Support docker wrapper

[dtretyakov]

We could provide support of building Unity projects in docker containers.

[phearbot]

This would be nice, particularly if there were a docker image paired with this plugin.

I found this repo recently and installed it on a TC server in a container, but have been having issues getting my agent container (built off of the minimal agent) to recognize the installed path no matter where I install it or how I pass the environment variable. (Tried -e when running the container as well as ENV in the Dockerfile) and I get "Unmet requirements: Exists=>unity.path..+ exists"

EDIT: I was able to get it to find it, but I had to install Unity in /root/Unity to do so. The above attempts didn't work, and I wrongfully assumed it would be running as the buildagent user as the only directory in /home/ in the TC docker container is buildagent.

[dtretyakov]

@phearbot, thanks for feedback. Could you please share what was the original path to Unity Editor in your image based on teamcity-minimal-agent?

In the latest plugin update it will honor /opt/Unity* and ~/Unity* paths to detect Unity installation. If you're using custom installation path you define UNITY_HOME pointing to Unity editor path, e.g. "/opt/Unity_2018.2".

And yes it seems that currently TeamCity build agent is started under default "root" user instead of builduser. We'll consider switching to using buildagent user in further versions: JetBrains/teamcity-docker-minimal-agent#16

[phearbot]

@dtretyakov, thanks for the awesome work! The path I originally had Unity installed in was /opt/Unity/, and I've downloaded the latest update and reverted back to that location in my agent and can confirm it does see it out of the box now. I think I was running into an issue with my environment variables not persisting, which is a docker thing more than likely.

I'm still ironing out issues one at a time that aren't related to the plugin (activating Unity in the container, etc.) but I'll keep testing the plugin as I work out the Unity side issues. Thanks again!

[dtretyakov]

@phearbot, in the latest plugin version also was added Unity build feature (#2) which may help you with Unity activation before starting TeamCity build and with returning this license after build completion. You could also try using it and share your feedback.

[AdamFrisby]

Being able to force the path in the build configuration, or via an environment variable which can be adjusted on a per-config basis would be useful.

We store all our Unity installs in C:\Unity* - it'd be nice if we could get the option to change the search directory from Program Files, et al - to there.

[lesley29]

Closing as this was resolved by TW-79001 and is available since version 1.1.0 of the plugin (note that you should be running TeamCity 2023.09+). The documentation is still in progress, but essentially the wrapper works as it does in all other runners. Here is a short excerpt from a script performing a discovery:

# The following sources are checked:
1) UNITY_ROOT_PARAMETER environment variable (can be set from agent's process)
2) UNITY_HOME environment variable
3) UNITY_HINT_PATH environment variable
4) PATH environment variable
5) /opt directory (for Linux)
6) /Applications directory (for MacOS)