This project is read-only.
1
Vote

Unable to Parse Build Number

description

We switched our build number to include the vcs number:

{0}.%build.vcs.number%

This causes Sharp2City to blow up. It is trying to parse the above string into an integer. TeamCity allows the build number to have non-numeric characters. For example:

{0}.MyBuild.%build.vcs.number%

is a valid build number format in TeamCity.

Sharp2City should probably parse this field as a string to more accurately represent the data it is getting back from TeamCity.

comments

theH0Tcarl wrote May 9, 2011 at 3:59 PM

I am uploading a patch now.