I have a project failure that triggered the following private message.
A new event has been added to the event log:
Action 'FinalBuilder [$Source.Iims-Hg-FinalBuilderProjects-Repo$\Iims_Build2.fbp7]' completed while not all message groups had been closed.
So I go and have a look at that build log and find an exception within the finalbuilder log. I can't seem to find a good reference to this specific exception.
devenv.com returned Error code: -107341502
I ran the same build project under Final Builder Server 7 and it worked without errors.
Are you able to take FinalBuilder out of the equation and just use the Visual Studio action in Continua CI to test this. I suspect the difference may be with how Continua CI executes processes. In FinalBuilder Server, we load the user profile for the user the build runs under (because the build service runs as networkservice), in Continua CI the agent runs as a specific user, and we do not load the profile.
What sort of VS project are you building? Is is possible to build with MSBuild? If so then set the action in FinalBuilder to use MSBuild. As much as I dislike MSBuild, it does provide better error reporting than devenv.
BTW, the evenlog entry is something we will need to look at, that suggests the FBCMD Continua Logger is not working as designed, which build of FinalBuilder are you using?
Latest editions of FBS 7.0.0.324 and FB7.7.0.0.1968. Will try and remove FB. I was just trying to do the least work possible for automated build upgrades from FBS 7 to continua.
“Stage awating agent” is not an error, it’s just informational, basically there is not an agent available to run the build. Go to the configuration page and the Agents tab, check there is an agent compatible with the configuration. If that is the case then on the agent check the windows event log, it’s possible something has gone wrong on the agent (although we try to have the agent report any errors to the continua eventlog that isn’t always possible).
I walked through those steps and even tried restarting the Continua service and Continua agents just in case. Suspect it’s a timing/threading issue. It didn’t seem to resolve the issue however. I’m thinking it might be better if I delete my DB and rebuild from scratch, just incase there is some dud data triggering these issues.
I’ll have a look at the MS Build configuration option, as I have that on a DNN module project, so it should be easier to drop in place. I’ll admit I’m throwing all my more complex builds at Continua, assuming you have all the basic ones all sorted out.
I’ll have a look at the MS Build configuration option, as I have that on a DNN module project, so it should be easier to drop in place. I’ll admit I’m throwing all my more complex builds at Continua, assuming you have all the basic ones all sorted out.
We certainly have no problem with you throwing your more complex builds at continua, the more the better I’ll do some investigation on this issue… at the moment I’m trying to figure out what kiln have done to make builds hang when cloning their repositories between the server and the agent… it’s been working fine for the last few weeks, but today it hangs. Local mercurial and also bitbucket mercurial repos are working fine.
I think they updated the ondemand account revision. There publicity of these “changes” is a little lacking. I’m having other troubles with them and HG as well.
Ok thanks, thats good to know. At the moment it looks like hg just hangs and doesn’t write anything to stdout or stderr, so it’s impossible to figure out what is going on.
