• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

sds / overcommit / 1537 / 2
91%
master: 91%

Build:
DEFAULT BRANCH: master
Ran 19 Jan 2018 05:11AM UTC
Files 176
Run time 2min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

19 Jan 2018 05:07AM UTC coverage: 89.963% (+0.05%) from 89.916%
2.1

push

travis-ci

sds
Add ChamberCompare hook

One of the pain points that can arise from adding settings to your
application is if you've set a new (required) item in `development` and
`test`, so it works locally and the tests pass, but you've forgotten to
set it in `production` (no, having a `staging` environment doesn't fully
alleviate this issue).

Then, you deploy your app only to have it blow up, which sets your
customers out with pitchforks for your head.

Fortunately Chamber provides an easy solution.  Whenever you commit
settings files, Chamber can automatically verify the settings of
multiple different namespace sets to ensure that they're all consistent.

For example, it can take `development`, `test` and `production` and
verify that all the keys that exist in one, exist in the other two.  If
that isn't the case, the hook will fail and the commit will abort.

You can enable it by creating an `.overcommit.yml` file and adding:

```yaml
ChamberCompare:
  enabled: true
```

This hook has an additional option:

| Name         | Description                                                                                                                                                                                             | Example                                       |
| ---          | ---                                                                                                                                                                                                     | ---                                           |
| `namespaces` | This is an array of arrays of namespaces to compare to each other. Typically each inner array will only have one item (the environment) but if you wanted to do a more intensive comparison, you could. | `[['development'], ['test'], ['production']]` |

2680 of 2979 relevant lines covered (89.96%)

100.81 hits per line

Source Files on job 1537.2 (2.1)
  • Tree
  • List 0
  • Changed 14
  • Source Changed 0
  • Coverage Changed 14
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 1537
  • Travis Job 1537.2
  • 69dc2927 on github
  • Prev Job for 2.1 on master (#1516.2)
  • Next Job for 2.1 on master (#1538.2)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc