Variables passed into Badge name only resolve to default values

[markusstephanides]

Hi!

When using parameters for the badge name, e.g. %env.platform%-%env.build_configuration%, looking at UnrealGameSync the badge created will only use the default values for the parameters instead of the actual passed parameters. I have also double checked, that the variables I used here are actually changed and set in the build.

Am I doing something wrong or does something need to be implemented into the plugin to re-resolve the variables?

[jorgenpt]

@markusstephanides I don't think any of our badges use that functionality, so I'll have to look into it. Is it true for all the statuses of your badge? It's possible that commit status publishers runs in a manner where it's not evaluating the variables in the context of the build job itself. I'll take a peek.

[markusstephanides]

Yes, it is. Thanks for looking into this!

[jorgenpt]

I've filed a ticket with TeamCity support about this, as I don't see anything obvious I'm supposed to do to expand them. The values are used verbatim from SBuildFeatureDescriptor.getParameters (as that's what's passed in to the plugin), and so if they're expanding to some value, then I don't even know how I'd go about getting the unexpanded variables and expanding them "correctly".

[jorgenpt]

Sounds like the default behavior of the parameters passed to commit-status-publisher is to resolve it without the context of the specific build (possibly because these can change during the run of the build). I am chatting with a TeamCity dev about the best way to address it in my plugin, if possible.

[markusstephanides]

Ok, thank you very much for the effort and keeping me posted!

[markusstephanides]

Hi, do you have any updates about this?
Thx!