Hello Forum Citizens !
We're using VS2008 add-on and TFS build server. The FBCMD.exe will be executed (see log file) and the build process waits for its completion endlessly. I have seen no generated log-file, which is normally done immediately after FBCMD runs a build. The FBCMD.exe takes 50% (dualcore) of the processor resources (Task manager). Installation of the previos version fixes the problem.
Regards and Thanks
001_BuildLog.txt (20.646 KB)Hi Matthias
It’s difficult to say what is causing this, we don’t see this issue here with our test TFS server. One thing to make sure is when you install the new version of FB that no builds are running. It’s possible a half finished update could cause problems immediately after startup.
Please contact support @ finalbuilder.com so we can work through this with you (we have a tool we can send you to figure out what fbcmd is doing when it is hung).
The issue was posted at support@finalbuilder.com.
I have more information about this problem now - i have tested the build profcess outside from the build service process, just typing a command line like this:
“C:\Program Files (x86)\FinalBuilder 6\FBCmd.exe” /MSBUILDMODE /#C"C:\Documents and Settings\TFSSERVICE\Local Settings\Temp\tmpF42A.tmp" /B /PD:\Builds\INSPECT\Core\BuildType\Core.fbp6.
If i use tmpF42A.tmp again in my test command line (which EXACTLY matches the temp file from TFS build) - it hungs. If i type for example tmpF123.tmp - it works ! And also interesting is, that all the temp files from normal builds are in the KB size, bu this tmpF42A.tmp is right after starting the FBCMD process is about 100 MB !
Regards,
Hi Matthius
The file in question contains the changeset/file information for the build. I’m not sure why the file would get so large, it’s possible I guess that the code that determines the changeset info is going too far back and recording every file/change (not sure why though). We may need to write some test code to see what is happening and send that to you as we are not able to reproduce the problem here. The way the code works it to look back as far as the last successful build, and then find all the changesets between then and the time the build started. The reason we have to do this is that TFS only records the changesets against a build once it’s completed successfully, which is too late for us.
Are you able to compress the file (it should contain xml, please check it first) and send it to us, or make it available for download somewhere. My guess is that FBMCMD is not hung, it’s just taking a long time to load/read and process the file.
Hi Matthias
Please try this build.
https://www.finalbuilder.com/downloads/finalbuilder/630/FB630_1739.exe
We adjusted how the fbcmd task discovers changesets. What is doing is getting the build history for a build, and then looping through the builds looking for the most recent successful build. If there were never any successful builds (there may have been partially successful, but it ignored those), it would get all the changesets for the project for the entire life of the project. I suspect that is what is happening here. The change we made was to also look at “partially successful” builds, and if no good builds were found then it will not return any changesets at all. This is safer than returning everything.
So when it looked like FBCMD had hung, it probably hadn’t, it was just taking the time to a) load the 100MB file, and b) processing the file and creating the Trigger Files collection in memory… both of which would take some time.
Hello Vincent,
The FB630_1739.exe solves the problem !
Can i use this as an official release, or should we wait for the next update from you ?
Regards
The only difference between the test builds and official releases is that we do more testing before a release. The build process is the same, so in most cases it is fine to use.
I’m glad to hear this build resolved the problem. In the build history for the project, did it ever have successful builds before?
For the test purposes i have created one new build definition. TFS project has a lot of other huge builds with “Partially succeeded” state and also “Succeeded”. The build with “Succeeded” am able to start, the builds with “partially succeeded” hungs. If i create any new build definition - it just hungs. In any case, your fix does solve this problem. Thank you !