Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Exit codes of the TravisCI shell scripts aren't propagated #48

Closed
Inkdpixels opened this issue Feb 29, 2016 · 0 comments
Closed

Exit codes of the TravisCI shell scripts aren't propagated #48

Inkdpixels opened this issue Feb 29, 2016 · 0 comments
Assignees
@Inkdpixels
Labels
Bug Label to mark the change as bugfix Tooling / Testing

Comments

@Inkdpixels
Copy link
Contributor

Thus, builds aren't breaking correctly as seen with https://travis-ci.org/PackageFactory/PackageFactory.Guevara/jobs/112261030

This will be solved by adding set -eat the top of each shell script.
@Inkdpixels Inkdpixels added Bug Label to mark the change as bugfix Tooling / Testing labels Feb 29, 2016
@Inkdpixels Inkdpixels self-assigned this Feb 29, 2016
Inkdpixels added a commit that referenced this issue Feb 29, 2016
@Inkdpixels
BUGFIX: Make sure that exit codes of commands in all shell scripts pr…
8d4d6a2 
…opagate their exit code correctly - closes #48
@Inkdpixels Inkdpixels mentioned this issue Feb 29, 2016
Merged
Inkdpixels added a commit that referenced this issue Feb 29, 2016
@Inkdpixels
Merge branch 'master' into task/updateESLint
74b4503 
* master:
  BUGFIX: Make sure that exit codes of commands in all shell scripts propagate their exit code correctly - closes #48
  TASK: Add color and progress output to the default build script
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Inkdpixels Inkdpixels

Labels
Bug Label to mark the change as bugfix Tooling / Testing
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Inkdpixels