Bug 25268 - Queued builds on TFS fails to generate IPA files
Summary: Queued builds on TFS fails to generate IPA files
Status: RESOLVED DUPLICATE of bug 26484
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: General ()
Version: 3.8
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2014-12-11 05:41 UTC by Prashant Cholachagudda
Modified: 2015-01-27 21:08 UTC (History)
5 users (show)

Is this bug a regression?: ---
Last known good build:

Build log (257.70 KB, text/plain)
2014-12-11 05:41 UTC, Prashant Cholachagudda

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Prashant Cholachagudda 2014-12-11 05:41:32 UTC
Created attachment 9028 [details]
Build log

When customer queques a build process, it appears to lose connection to the build host in the middle of its process, and ends up without creating an IPA file. 

Customer can successfully built a project as local/TFS user with `msbuild` command
    msbuild c:\main\eoTouch\eoTouch.csproj /t:Build

 But, as soon as they redirect output to a file, with following command

 	C:\Windows\Microsoft.NET\Framework64\v4.0.30319>msbuild c:\main\eoTouch\eoTouch.csproj /t:Build >c:\what\buildlog1.txt 2>&1

They get fail to resolve address error, see buildlog1.txt for complete log
	  Fail to resolve address
Comment 2 Brendan Zagaeski (Xamarin Team, assistant) 2015-01-27 21:08:06 UTC
Thanks for the report. I'm marking this bug as a duplicate of bug 26484 because based on the log file from comment 0 I'm fairly confident it's the same issue and because the new bug has precise "steps to reproduce" and "results" sections.

*** This bug has been marked as a duplicate of bug 26484 ***