6
91%
master: 91%

Ran 05 Apr 2018 10:39PM UTC

Files 33

Run time 1s

Badge

Embed ▾

Committed 05 Apr 2018 10:12PM UTC coverage: 90.817% (+2.0%) from 88.797%

Job # 2.3.0, BUNDLE_VERSION=1.12.0 GEMSETS="test sidekiq coverage"

Build Type

push

travis-ci

Committed by

kattrali

Commit Message

fix(rails): Log missing key warning after Rails initialization completes

When not initializing using the BUGSNAG_API_KEY environment variable,
the first time the Railtie integration is loaded, no API key is
available. At the bottom of the configure method, a warning is emitted
stating that no API key has been set, though this may not be true after
config/initializers/bugsnag.rb runs. This is the behavior being observed
in #391, causing concern that bugsnag is not working correctly when in
fact the log message is premature.

This change allows for Bugsnag.configure to be called without validating
the key, allowing the Railtie integration to add an additional check
once Rails initialization is complete.

Fixes #391

Run Details

989 of 1089 relevant lines covered (90.82%)

3422.47 hits per line

bugsnag / bugsnag-ruby / 1730 / 6
91%
master: 91%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 1730.6 (2.3.0, BUNDLE_VERSION=1.12.0 GEMSETS="test sidekiq coverage")

bugsnag / bugsnag-ruby / 1730 / 6 91% master: 91%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 1730.6 (2.3.0, BUNDLE_VERSION=1.12.0 GEMSETS="test sidekiq coverage")

bugsnag / bugsnag-ruby / 1730 / 6
91%
master: 91%

README BADGES
x