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.

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

Exit with non-zero status code on .travis.yml with issues #4

Merged
merged 3 commits into from Feb 27, 2012

Conversation

dvberkel
Copy link
Contributor

This solves issues #3.

Travis::Lint::Runner has a one-line change i.e. to quit with a non-zero exit code when issues are found with the .travis.yml file.

This behavior is specified in a spec file: travis_lint_runner_spec.rb.

When issues are found with the .travis.yml file exit with a non-zero
status code.

This resolve issue [#3](https://github.com/travis-ci/travis-lint/issues/3 "Issue #3 for travis-lint").

Note: Feature is tested by hand. I will add a spec for this in a
later commit.
If a .travis.yml file has issues the Travis::Lint::Runner should
exit with a non-zero exit status. This is capture in the
travis_lint_runner_spec.rb
The test run should not interfere with the rspec output. Therefore
stdout is capture by an instance of StringIO.
@michaelklishin
Copy link
Contributor

Thank you. Extra points for adding specs that capture stdout.

michaelklishin added a commit that referenced this pull request Feb 27, 2012
Exit with non-zero status code on .travis.yml with issues
@michaelklishin michaelklishin merged commit feb93a3 into travis-ci:master Feb 27, 2012
@michaelklishin
Copy link
Contributor

We will release next travis-lint version later this week

@dvberkel
Copy link
Contributor Author

Great! looking forward to it.

@michaelklishin
Copy link
Contributor

1.3.0 is up on rubygems.org

@dvberkel
Copy link
Contributor Author

dvberkel commented Mar 7, 2012

Great, I will upgrade to 1.3.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants