3

I'm trying to get a project to work with a continuous integration build. Currently, it consists of a library dll, .net 4.5 app, and WP8 app. I use team foundation service with GIT as my source control.

I was able to set up a build configuration but it fails with the following message:

Exception Message: MSBuild error 1 has ended this build. You can find more specific information about the cause of this error in above messages. (type BuildProcessTerminateException)
Exception Stack Trace:    at System.Activities.Statements.Throw.Execute(CodeActivityContext context)
   at System.Activities.CodeActivity.InternalExecute(ActivityInstance instance, ActivityExecutor executor, BookmarkManager bookmarkManager)
   at System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor executor, BookmarkManager bookmarkManager, Location resultLocation)

This is the ONLY exception in the entire solution, although there are 10 warnings. Additionally, I've run the build with the verbosity to diagnostic and here is the output of that.

Again I don't see any issues with that build, just the cryptic "Done building project.... --FAILED" message. Locally, the project can be built and rebuilt without any issues. Anyone have any idea what might be causing this issue?

Edit: Through trial and error I've narrowed the issue down to having a windows phone 8 application in my solution. If I exclude that project, the solution builds fine. If it's included, I get the problem. Should I perhaps be using a separate build definition for each project and not for the solution itself? Windows phone 8 projects by themselves build fine...

steveg89
  • 1,807
  • 2
  • 15
  • 29

1 Answers1

3

The error you're getting is occurring within the build template that your build definition is using. Build templates are Windows Workflow files that guide TFS Build through the process of executing a given build. The reason why your project is building locally is that Visual Studio isn't using this build template, as build templates only run on the server under TFS Build.

I dare say someone has customised the build template that your build is using, and that customisation is failing. Based on the error, it seems to be happening during the execution of a CodeActivity, which is now obsolete (though being obsolete isn't actually the issue). The custom code in that CodeActivity is probably failing though.

Assuming your build process doesn't need any specific customisations provided by the failing build template, I'd just select a different one or create a new one. You can do this from the Process tab when editing the build definition.

Hope this helps!

Chris Anderson
  • 8,279
  • 2
  • 20
  • 18
  • I'll give it a try. This is a perfectly clean template other than a few flags. I changed the build processor to x86 so that Windows Phone would build properly, then I specified to build Release for Any CPU. I will try this when I get home. If it doesn't work, is there anything I can post that would help you narrow it down? Pics of the build setup perhaps? – steveg89 Aug 12 '13 at 11:07
  • Do you have any other builds working successfully on this build server? Can you try creating a simple console app and getting the build server to build it using the same build template? That will prove whether or not it's the build template being the problem. You're building a WP8 app - do you have the SDK installed on the build server? Also, which version of TFS are you using? If TFS2010, you'll need the .NET Framework 4.5 installed on the build server. – Chris Anderson Aug 13 '13 at 00:40
  • 1
    This is all using team foundation service, so I'm not in control of the build server at all. – steveg89 Aug 13 '13 at 11:01
  • Ah, OK. Well then I'd expect it would have all of this stuff installed then. Can you post the warnings you're getting please? – Chris Anderson Aug 13 '13 at 12:59
  • I'm at work but they are for assigning a variable to itself. It's definitely things that can be taken out, but I wouldn't think that would be necessary... There are 10 of those warnings. – steveg89 Aug 13 '13 at 13:02
  • Hmm, OK. I'd try removing parts of your build to see if you can narrow down the issue to a particular project being built. For example, just try getting it to build your DLL. If that doesn't work, create a console app like I mentioned and get it to build that. Basically remove most things so it works (hopefully), then gradually add things back in until it fails, thus narrowing the issue down. – Chris Anderson Aug 13 '13 at 13:05
  • I'll work on that tonight and update my question with the results. Thank you for looking into this – steveg89 Aug 13 '13 at 13:07
  • OK, I'm afraid I have to admit to being utterly flummoxed with this issue. The fact that you can build a WP8 project file on its own, but not in a solution with other projects is baffling. At least the issue has been identified now. I'd say it's a TFS bug given the info you've provided - I can't think of any other rational reason for that behaviour. If it's OK to use separate build definitions to build your projects then I think that's a solution for now. Create separate solutions for the build server, and keep the current one to use for dev. – Chris Anderson Aug 14 '13 at 03:56
  • Also, report it as a bug on Connect and see what they say. – Chris Anderson Aug 14 '13 at 03:56
  • I know we didn't come to a real solution, but I'm going to give you the answer flag as someone else may be able to follow your steps to correct their issue. – steveg89 Oct 15 '13 at 20:29
  • Thanks Steve :). Sorry to hear your issue still hasn't been resolved, but hopefully the problem will be solved in the near future. – Chris Anderson Oct 16 '13 at 00:48