You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was under the impression that when the Buildrunner runs I can even only provide the minor Unity version, e.g.:
2018.2
2019.4
2020.3
So I don't have to specify the exact Unity version. I thought the runner will just pickup a random installed version of Unity, for example, I set 2018.2 as the Unity version it'll look at the installed 2018.2 versions like
2018.2.1f1
2018.2.4f1
and so on and pick randomly one and build the project with that.
But apparently that's not the case?
I just tried that with my Unity 2020.3.0f1 installation.
In my buildstep I set "2020.3" as the Unity version and build the project, but immediately an error was thrown:
[17:24:10] jetbrains.buildServer.agent.ToolCannotBeFoundException: Unable to locate tool unity 2020.3 in system. Please make sure to specify UNITY_PATH environment variable
I looked at my path variables and it sure exists: "unity.path.2020.3.0"
I also tried different string variations:
2020.3
2020.3.
2020.3.*
All of them threw the same error. Of course when I set the version specifically to 2020.3.0 it worked like a charm.
I hoped I could just threw in the minor version there without the need to specify the patch version, since that's extra work for me to go through every buildconfig every time we update the Unity version to a new patch version.
Is that a bug? Did I forget something?
The text was updated successfully, but these errors were encountered:
Hey there,
I was under the impression that when the Buildrunner runs I can even only provide the minor Unity version, e.g.:
2018.2
2019.4
2020.3
So I don't have to specify the exact Unity version. I thought the runner will just pickup a random installed version of Unity, for example, I set 2018.2 as the Unity version it'll look at the installed 2018.2 versions like
2018.2.1f1
2018.2.4f1
and so on and pick randomly one and build the project with that.
But apparently that's not the case?
I just tried that with my Unity 2020.3.0f1 installation.
In my buildstep I set "2020.3" as the Unity version and build the project, but immediately an error was thrown:
[17:24:10] jetbrains.buildServer.agent.ToolCannotBeFoundException: Unable to locate tool unity 2020.3 in system. Please make sure to specify UNITY_PATH environment variable
I looked at my path variables and it sure exists: "unity.path.2020.3.0"
I also tried different string variations:
All of them threw the same error. Of course when I set the version specifically to 2020.3.0 it worked like a charm.
I hoped I could just threw in the minor version there without the need to specify the patch version, since that's extra work for me to go through every buildconfig every time we update the Unity version to a new patch version.
Is that a bug? Did I forget something?
The text was updated successfully, but these errors were encountered: