Allow use of a configuration parameter for the Unity Version

[fklingler]

Hello!

I'd want to use a teamcity Configuration Parameter to configure the Unity Version, so my team can easily swap the version used when running a build (notably using the "custom run" button).

Unfortunately, this doesn't seem to work, as my agent is shown as incompatible:

It doesn't seem that the configuration parameter is interpreted before the unity version is tested for the agents

[dtretyakov]

@fklingler, at the moment TeamCity does not support parameters resolution in agent requirements: https://youtrack.jetbrains.com/issue/TW-5661

You could vote/watch for the mentioned issue.

[fklingler]

Thanks, I will do that!

FYI, this enhancement you suggested https://github.com/JetBrains/teamcity-unity-plugin/issues/19 would also allow me to do what I want! It's in fact how we did it previously with an old teamcity unity plugin.

[ArtOfSettling]

Is there anyway we can build the runner to work around this issue? I'm also facing it and for now i'm just disabling the requirement check on my fork and using that rather than the official plugin. (We rely heavily on metarunners with parameters)

[AaronZurawski]

Without this feature, updating several build configs that are all based on a handful of different templates becomes monotonous and error-prone. With a parameterized field, its a simple, easily-enforceable change.

I've voted for the related TeamCity feature request as well.

[tallior]

@dtretyakov i realize TC doesn't support parameter resolution in agent requirements, but is there a way to overcome this, for example, by re-working how this mechanism works (e.g: don't use agent requirements) ?

This is a really basic requirement (setting different Unity versions) and the fact it's not working makes it very difficult to work with this plugin.

[dtretyakov]

@NikolayPianikov maybe we could somehow overcome this issue?

[AaronZurawski]

I have submitted a PR #54 that adds support for TeamCity to be managed as a TeamCity agent tool. This may provide a viable alternative to solve this issue.

[lesley29]

It seems like a bit irrelevant issue was mentioned here earlier. As I can see, TC does support property resolution in agent requirements since 2020.2 EAP3. Relevant links:

• https://github.com/JetBrains/teamcity-unity-plugin/issues/51
• https://youtrack.jetbrains.com/issue/TW-19877/Support-property-resolution-references-to-agent-parameters-in-agent-requirements

Please feel free to reopen this issue if you are still running into the described problem.