You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cordova.apache.org by "Ian Clelland (JIRA)" <ji...@apache.org> on 2013/05/13 15:01:18 UTC

[jira] [Commented] (CB-3376) cordova build ios fails silently

    [ https://issues.apache.org/jira/browse/CB-3376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13655941#comment-13655941 ] 

Ian Clelland commented on CB-3376:
----------------------------------

The build script should exit with the status of the xcodebuild command; it's the last command in the script.

>From the xcodebuild man page,

{panel}
   *Exit Codes*

       *xcodebuild* exits with codes defined by sysexits(3).  It will exit with *EX_OK* on success.  On failure, it will commonly exit with
       *EX_USAGE* if any options appear malformed, *EX_NOINPUT* if any input files cannot be found, *EX_IOERR* if any files cannot
       be read or written, and *EX_SOFTWARE* if the commands given to xcodebuild fail.  It may exit with other codes in less common
       scenarios.
{panel}

I would think that any CI system should be able to interpret that status -- is there additional output that would be more useful?
                
> cordova build ios fails silently
> --------------------------------
>
>                 Key: CB-3376
>                 URL: https://issues.apache.org/jira/browse/CB-3376
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: CLI
>    Affects Versions: 2.6.0
>         Environment: OSX
>            Reporter: Andrew Smith
>            Assignee: Filip Maj
>
> When running a build, if the xcodebuild command fails, there is no output or notification.
> This is especially painful when running a continuous integration system, or build runner (like grunt), as it thinks all is fine, but just as bad when doing an individual build, as you have no idea if there was a problem, until you try and install the app.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira