Since the last update (3033), it seems that the first build of the day (or at least service restart) is dying because the schema version is in a bad format.
All other builds (of the day) work perfect.
In the build log, i can see that our batch script is still getting and setting (via console output) the correct version into the variable.
The “Set Build Version” then says:
Build version has been set to ‘0.0.0.0.2591’.
Ok, 5 parts, all zero and the last is the incremented build number. Thats definitely wrong.
Sorry, can’t give you more information at this time.
Can you confirm how you are setting the build version? What is the exact output from your batch file?
[code]:: read value and create dynamic variableFOR /F "tokens=1,2,3,4 delims=." %%a IN ('FINDSTR /I AssemblyVersion …\Code\CareSchema\AssemblyInfo.vb') DO (SET MAJOR=%%aSET MINOR=%%bSET BUILD=%%cSET REVISION=%%d)SET SCHEMAVERSION=%MAJOR:~-1%.%MINOR%.%BUILD%:: special output so build server will update variable values (https://www.finalbuilder.com/support/forums/aft/11632.aspx)echo @@log{setvariable name="SchemaVersion", value="%SCHEMAVERSION%"}[/code]
i can see, that in the failing builds the message is missing that continua outputs if a variable changes:
Variable ‘%schemaversion%’ has been set to ‘4.2.1151’.
well, the last line is an “echo” from our script but this is empty, too. so it seems, its empty string, but i don’t know why. a second build (e.g. triggered manually works). is continua printing no output if the new value of the variable is empty? otherwise a message like this should be printed:
Variable ‘%schemaversion%’ has been set to ‘’.
we use the “Set Build Version” action with the value “%SchemaVersion%.$Build.BuildNumber$”
the output of a failed build:
[code]Variable ‘%schemaversion%’ has been set to ‘4.2.1151’. 4.2.1151Build version has been set to ‘0.0.0.0.2608’.[/code]
so it assume the output stuff from our script is correct and somethings wrong in the action itself.
We’re still looking into this. Dave thinks i may be addressed by another fix he was working on, it’s awaiting code review today so we’ll test this today.
Hi Christian,
I’ve not managed to specifically replicate the issue running your batch file. We have, however, identified an bug where the output from running processes could be lost if sent after the process ends.
I suspect this may be the cause of your issue. Please install the following version and let us know whether your build still fails:
ContinuaCI Server v1.0.0.3054
ContinuaCI Agent v1.0.0.3054
ok, i’ve installed the version. lets see what the time brings.
Apologies, but the last build omits newline characters from the process output and this didn't come up in our testing.
Please install the following fix:
ContinuaCI Server v1.0.0.3060
ContinuaCI Agent v1.0.0.3060
both seems to be fixed. thank you again for the fast and good support. great work.