Bug 45138 - xbuild exit code 0 even on build failure
Summary: xbuild exit code 0 even on build failure
Alias: None
Product: Tools
Classification: Mono
Component: xbuild ()
Version: 4.2.3 (C6SR3)
Hardware: PC Linux
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2016-10-06 21:17 UTC by mnowak
Modified: 2018-03-15 10:40 UTC (History)
2 users (show)

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

Xbuild output along with exit code (10.09 KB, text/plain)
2016-10-06 21:17 UTC, mnowak

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 GitHub or 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 mnowak 2016-10-06 21:17:18 UTC
Created attachment 17916 [details]
Xbuild output along with exit code

We have an issue with xbuild exiting 0 even when stating the build has failed and displaying all the errors.  This is leading to our CI system markings builds as successful even though they are not.  Our environment is a docker container running centOS 7.2.1511 and the issue occurs using mono and  See attached log for build output for both and followed by the exit code of the command.
Comment 1 Marek Safar 2018-03-15 10:40:08 UTC
We deprecated xbuild and recommend using msbuild instead. Switching to msbuild will also most likely resolve the issue you reported.