Titanium JIRA Archive
Alloy (ALOY)

[ALOY-1167] Update travis.yml to exit w/non-zero value on errors

GitHub Issuen/a
Resolution Date2014-10-28T02:31:50.000+0000
Affected Version/sn/a
Fix Version/sAlloy 1.6.0
ReporterTim Poulsen
AssigneeTim Poulsen


GitHub builds are marked as passing even when errors are encountered by Travis. Our test scripts must be exiting with a non-zero value in the case of errors. We should add an after_script section that exits with 0/non-zero to properly signal build state. http://docs.travis-ci.com/user/build-configuration/


  1. Tim Poulsen 2014-10-21

    PR https://github.com/appcelerator/alloy/pull/595 I'm not sure how you can test this, as this change is entirely for the Travis environment on our GitHub repo. Perhaps simply checking the travis build log (click the "Details" link) on the pull request page is the only way to test it. You should see that all tests pass, no failures are reported, and ultimately the build is marked as passing. Prior to this change, even when individual tests failed, the overall PR would be marked as passing.
  2. Feon Sua Xin Miao 2014-10-23

    PR merged.
  3. Tim Poulsen 2014-10-24

    Reopen for 1_6_X backport
  4. Tim Poulsen 2014-10-24

    PR https://github.com/appcelerator/alloy/pull/610
  5. Feon Sua Xin Miao 2014-10-28

    PR merged.
  6. Eric Wieber 2015-03-26

    Verified fixed using: Alloy 1.6.0-alpha Successful tests exit with zero while tests with errors exit with non-zero values.

JSON Source