VCS Labeling issue (prefix/leading space)

What do you have in the "Labeling Pattern" field on the VCS Labeling Build Feature? Would you be able to share a screenshot of this entire menu (redacting anything confidential)? 

Hi Eric,

here are the screenshots.

Thanks! Since you've defined the label as %system.build.number%, can you also share a screenshot of the "Build Number Format" field in the general settings for this build configuration?

I overwrite the build number during the build

Can you please describe how you are overwriting the build number during the build? I can't seem to replicate this on my end.

Hi Eric,

I found the error and here is how it can be reproduced. You need the Powershell Runnter to replace the build.number. I am no PowerShell expert, so this might even be expected behavior...

WORKING VERSION:

----

$version = "1.0.0-pre1";

#Does NOT add space prefix
$var4a = "Setting buildNumber to " + $version;
$var4b = "##teamcity[buildNumber '" + $version + "']";

Write-Host $var1a;
Write-Host $var1b;

NON-WORKING VERSION:

-----

$version = "1.0.0-pre1";

#Adds space prefix
Write-Host "Setting buildNumber to "$version
Write-Host "##teamcity[buildNumber '"$version"']"

----

Thanks for writing back to share your findings. It seems like this command has a generous amount of quotation marks:

Write-Host "##teamcity[buildNumber '"$version"']"

By enclosing $version in single quotes, your non-working version works for me:

$version = "1.0.0-pre1";
Write-Host "Setting buildNumber to "$version
Write-Host "##teamcity[buildNumber '$version']"

Mhm. This line:

Write-Host "Setting buildNumber to "$version

creates this output with 2 spaces in the build log:

Setting buildNumber to  1.0.0-pre