Using configuration parameter for required Unity version causes agent requirement to fail

mindcandy / Teamcity-unity3d-build-runner-plugin

A Teamcity plugin for building Unity3d projects. NOTE: this has an MIT license so feel free to copy / adapt as you need to.

107 stars 59 forks source link

Using configuration parameter for required Unity version causes agent requirement to fail #28

Open Chippit opened 9 years ago

Chippit commented 9 years ago

Attempting to use a TeamCity configuration parameter for the Unity version in a build step causes agent requirements to fail with a message below (assuming %unityVersion% is the defined parameter), rather than correctly resolving the parameter for the check.

Unmet requirements: unity.%unityVersion% exists

MHAbrah commented 9 years ago

This is a major problem, forcing duplicate templates for each version of Unity that needs to be supported. Does anyone have a work-around for this issue?

weltenbauer commented 8 years ago

Possible workaround for the issue:

Leave Unity-Version and Unity-Executable field in the build step setting blank
Create a symbolic link from "C:\Program Files (x86)\Unity" to "C:\Program Files\Unity (YOUR-VESION)" by using the cmdline tool "mklink /J"