They could be found on the Agents -> "%agentName%" -> Agent Parameters -> Configuration Parameters page in TeamCity server UI. Agent configuration parametersĪll detected Unity versions will be reported as build agent configuration parameters with the unity.path.%unityVersion% prefix. Multiple paths could be specified by using default path delimiter. To search Unity installation directories in custom path matching Unity* pattern you could use UNITY_HINT_PATH environment variable, e.g. To add Unity installation located in custom path you could use UNITY_HOME environment variable, e.g. Note: you need to start TeamCity build agent under the same user account which is used for Unity Hub installation. TeamCity agent tools location, which allows installing Unity as an agent tool.
Windows: %Program Files%/Unity* and %Program Files%/Unity/Hub/Editor/*.Linux: /opt/Unity*/ ~/Unity* and /opt/Unity/Hub/Editor/*/ ~/Unity/Hub/Editor/*.Also it searches Editors in the PATH environment variable and in the following well-known directories: The plugin automatically detects Editors installed via Unity Hub. The plugin is compatible with TeamCity 2018.1+ and was verified to work with Unity 2017+. Note: After installation, you need to restart TeamCity server by going to Administration => Diagnostics => Restart Server Compatibility
#Teamcity hack install#
You can download the plugin and install it as an additional TeamCity plugin.
#Teamcity hack license#
This TeamCity build feature allows to automatically activate and return Unity Editor license before build start and after build completion.Īlso it allows to configure Unity cache server address in one place to use this setting within Unity build steps.
0 kommentar(er)
