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

sds / overcommit / 1537
91%

Build:
DEFAULT BRANCH: master
Ran 19 Jan 2018 05:09AM UTC
Jobs 5
Files 176
Run time 4min
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

pending completion
1537

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']]` |

2695 of 3004 relevant lines covered (89.71%)

499.87 hits per line

Jobs
ID Job ID Ran Files Coverage
1 1537.1 (2.0) 19 Jan 2018 05:10AM UTC 0
90.0
Travis Job 1537.1
2 1537.2 (2.1) 19 Jan 2018 05:11AM UTC 0
89.96
Travis Job 1537.2
3 1537.3 (2.2) 19 Jan 2018 05:09AM UTC 0
89.68
Travis Job 1537.3
4 1537.4 (2.3.0) 19 Jan 2018 05:10AM UTC 0
89.96
Travis Job 1537.4
5 1537.5 (2.4.1) 19 Jan 2018 05:10AM UTC 0
89.71
Travis Job 1537.5
Source Files on build 1537
Detailed source file information is not available for this build.
  • Back to Repo
  • Travis Build #1537
  • 69dc2927 on github
  • Prev Build on master (#1516)
  • Next Build on master (#1538)
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