Open magnusfox opened 4 years ago
i read somewhere that the hub CLI is really unstable. not sure if it's right or not - just be aware that it might not really work
On Thu, Oct 1, 2020 at 12:40 PM magnusfox notifications@github.com wrote:
Unity is releasing a new version about every week, and during the development phase of a game the version used can be changed frequently. Currently this means we have to install new versions manually on each of our agents, plus reboot the agent to make it aware of the new Unity version.
One suggestion is to use the Unity Hub CLI to install versions (or modules) on the fly from this runner, if the wanted version (or module) is not present upon launch. This should probably be optional, to avoid installing versions unintentionally.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/JetBrains/teamcity-unity-plugin/issues/52, or unsubscribe https://github.com/notifications/unsubscribe-auth/AB3RFPQYXK2WBDGZ7AP3SO3SIRE73ANCNFSM4SAF57SA .
TeamCity is not responsible for installing components on an agent except TeamCity agent tools. Actually these tools are archives and ready to use after unpacking. Looks like Unity requires an installation process. As alternative I am ready to try creating a docker Image based on https://hub.docker.com/r/jetbrains/teamcity-minimal-agent with tracking of a latest Unity version. Another option is to use TeamCity Docker Wrapper and to use any images with Unity to run builds in this case I might add the supporting of Docker Wrapper for this plugin.
Even if the plugin doesn't support installing the different versions, it would be great if there was a way to make it update the available versions on the fly
I can make sure the correct version is installed as part of the job script, but then the unity plugin doesn't know that I've installed the correct version without restarting the agent which has to be done manually
Unity is releasing a new version about every week, and during the development phase of a game the version used can be changed frequently. Currently this means we have to install new versions manually on each of our agents, plus reboot the agent to make it aware of the new Unity version.
One suggestion is to use the Unity Hub CLI to install versions (or modules) on the fly from this runner, if the wanted version (or module) is not present upon launch. This should probably be optional, to avoid installing versions unintentionally.