Users wonder why their build doesn’t start, but often the culprit is
.travis.yml. We introduced our web linter as tool to validate a
.travis.yml. Until recently, this solution was far from ideal. Most settings were simply ignored, and those that were validated often resulted in false positives. This tool wasn’t all that useful.
We have now replaced it with a complete rewrite. It is using our brand new travis-yaml gem. This means instead of being very rudimentary and not well maintained, it is powerful and descriptive when it comes to spotting issues in your build configuration.
Having a new linter was just a byproduct of creating the travis-yaml library. We plan to use this small gem throughout our system. That way we will have one central definition for the
First, we need to get 100% coverage of the currently supported configuration options, though.
Why don’t you give the new linter a try and tell us what you think?