Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
markdonghan opened this issue Mar 13, 2020 · 9 comments
Open

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

markdonghan opened this issue Mar 13, 2020 · 9 comments
Assignees
Labels
bug Something isn't working

Comments

@markdonghan
Copy link

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
Copy link
Author

@dtretyakov

@dtretyakov
Copy link
Collaborator

@NikolayPianikov could you please assist with it?

@dcam0050
Copy link

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?

@albermotion
Copy link

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

@NikolayPianikov NikolayPianikov self-assigned this Oct 12, 2020
@NikolayPianikov NikolayPianikov added the bug Something isn't working label Oct 12, 2020
@NikolayPianikov
Copy link
Contributor

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.

@kakacoding
Copy link

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

@amelkor
Copy link

amelkor commented Nov 5, 2020

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.

@HashbangGames
Copy link

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

@gopokyo-colinn
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

9 participants