[jira] [Comment Edited] (AURORA-1138) aurorabuild.sh should exit on error in any command

["Thorhallur Sverrisson (JIRA)" <ji...@apache.org>]

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

Thorhallur Sverrisson edited comment on AURORA-1138 at 2/23/15 12:09 AM:
-------------------------------------------------------------------------

I have a patch ready that enables the -e on the bash scripts used in vagrant.  I'm not sure why, but after having what seems like a successful build aurora-scheduler upstart log contains nothing but:
{code}
Could not find or load main class org.apache.aurora.scheduler.app.SchedulerMain
{code}

I'm trying to figure out why, but gradle is new to me so I'm not sure why it is not being built/included in the .jar files.

I have submitted a review request for the changes I made: https://reviews.apache.org/r/31289/


was (Author: thorhs):
I have a patch ready that enables the -e on the bash scripts used in vagrant.  I'm not sure why, but after having what seems like a successful build aurora-scheduler upstart log contains nothing but:
{code}
Could not find or load main class "org.apache.aurora.scheduler.app.SchedulerMain"
{code}

I'm trying to figure out why, but gradle is new to me so I'm not sure why it is not being built/included in the .jar files.

I have submitted a review request for the changes I made: https://reviews.apache.org/r/31289/

> aurorabuild.sh should exit on error in any command
> --------------------------------------------------
>
>                 Key: AURORA-1138
>                 URL: https://issues.apache.org/jira/browse/AURORA-1138
>             Project: Aurora
>          Issue Type: Bug
>          Components: Build
>    Affects Versions: 0.7.0
>         Environment: Vagrant from examples/vagrant
>            Reporter: Thorhallur Sverrisson
>            Priority: Trivial
>              Labels: easyfix
>
> Due to proxy issues the mesos native egg could not be downloaded, but the scripts continued to completion.  This resulted in termos_observer.pex being a plain .zip file which failed to execute.
> Not many hits on google regarding that issue, but I managed to find a link to an issue where the native egg had been moved from mesosphere to svn.apache.org which led me to rerun the 'aurorabuild.sh executor' and watching the output more closely.  Lo and behold there was an error in the compilation.
> Having a 'set -e' at the top of the provision and aurorabuild scripts would have indicated the problem right away.  It could also flush out other issues that may be present.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)