teamcity-unity-plugin icon indicating copy to clipboard operation
teamcity-unity-plugin copied to clipboard

cannot fix Unmet requirements: Exists=>unity.path.xxx

Open markdonghan opened this issue 4 years ago • 9 comments

I've done following steps: 1.start TeamCity build agent under the same user account which is used for Unity Hub installation 2.add Unity installation located in custom path you could use UNITY_HOME environment variable But still not ok. I don't know what i should try next,or maybe just give it up and use Jenkins. Really need help. Give me a clue please. 1 2 3

markdonghan avatar Mar 13 '20 17:03 markdonghan

@dtretyakov

markdonghan avatar Mar 13 '20 17:03 markdonghan

@NikolayPianikov could you please assist with it?

dtretyakov avatar Mar 14 '20 08:03 dtretyakov

I have observed the same issue when using this plugin within docker running Ubuntu 18.04 and unity install location /opt/Unity

It seems that previous to and including 2019.1.14 the plugin recognises the presence of a unity tool.

However from 2019.2.0 onwards up to the most recent version (2020.1.0) the plugin doesn't recognise the unity installation.

Is there a way I could investigate further?

dcam0050 avatar May 25 '20 23:05 dcam0050

Same problem here, I have double-checked that the path is correct (Unity Hub installed Unity under ~/Unity/Hub/Editor folder), but agent doesn't seem to find it

albermotion avatar Jul 17 '20 08:07 albermotion

Unfortunately I cannot reproduce this issue, I've added logs. Could you try installing this plugin and attach teamcity-agent.log after TeamCity agent restart.

NikolayPianikov avatar Oct 12 '20 11:10 NikolayPianikov

I have the same problem, I found that this function cannot get the version of Unity. val version = PEUtil.getProductVersion(executable) ?: return@forEach @NikolayPianikov

kakacoding avatar Nov 02 '20 04:11 kakacoding

It doesn't work through specifying the version as a TeamCity parameter like: %my.unity.version%

That leads to: Incompatible configurations Unmet requirements: Exists=>unity.path.%my.unity.version%.* exists

And typing 2020.1.11 in the version field directly in build step settings works.

amelkor avatar Nov 05 '20 16:11 amelkor

I am also having this issue image

@amelkor suggestion did not work for me. I am running TeamCity w/ Docker on OSX Big Sur 11.5.2

HashbangGames avatar Sep 01 '21 17:09 HashbangGames

I also have this issue. I have tried typing in the unity version. I have verified that Unity editors are installed where they should be found. On Ubuntu

gopokyo-colinn avatar Nov 03 '21 08:11 gopokyo-colinn