[Jenkins-infra] Using Rollbar.com JS error reporting in Blue Ocean plugin

James Dumay jdumay at cloudbees.com
Fri Jun 24 05:31:43 UTC 2016


That works for me. I'm happy to post on the dev list about our usage a few
weeks in to see if anyone else wants to use it.

Ill merge it.

On Fri, Jun 24, 2016 at 2:04 PM R. Tyler Croy <tyler at monkeypox.org> wrote:

> (replies inline)
>
> On Wed, 22 Jun 2016, James Dumay wrote:
>
> > Hi all,
> >
> > The Blue Ocean plugin is very JavaScript heavy and is prone to problems
> > that we can only see on the web client.
> >
> > We want to use Rollbar.com to collect, collate and report web client
> > errors. It is one of the most common tools that help solve this problem.
> >
> > There is a PR in review that will add this to every Blue Ocean plugin
> > screen https://github.com/jenkinsci/blueocean-plugin/pull/286
> >
> > I got in touch with Daniel Steuernol from Rollbar and asked him if it
> would
> > be suitable for use in OSS. He replied saying:
> >
> > *Hey there, absolutely that would be great, we do have an option that
> where
> > you can turn the project on rollbar to be a public project. We don't
> have a
> > formal process around this yet, but if you wanted to go this way, we
> would
> > put you on the Growth plan (1.5m events/month) to start, and if that
> isn't
> > sufficient we could re-assess once we see what the usage is like, another
> > option would be our partner plan, where if you add our badge to your
> source
> > control repo page, and on the site where Rollbar is being used we will
> add
> > 50,000 events per month. Let me know if you have any other questions and
> > I'll be happy to help!*
> >
> > I think that means we can allow anyone in the project to see those error
> > reports.
> >
> > I asked about anonymised data collection too:
> >
> > *For people tracking, that's opt-in with Rollbar, so by default we don't
> > track anything about the user and it has to be specified explicitly. *
> >
> > I did notice that by default they do collect IP addresses but I was able
> to
> > make it specify a fake one (0.0.0.0) for all requests (this is reflected
> in
> > the PR).
> >
> > Are their any major objections to using this service?
>
>
> I don't have major objections to using this service for the Blue Ocean
> plugin.
> This becomes a more challenging problem if other plugins also want to ues
> it,
> or if we want to centralize error reporting for multiple plugins.
>
> The biggest challenges would be authentication and access control, my two
> favorite frownies.
>
>
>
> If this turns out to be useful for Blue Ocean and we want to use it
> elsewhere,
> let's cross that figurative bridge when we get there.
>
>
>
>
>
> - R. Tyler Croy
>
> ------------------------------------------------------
>      Code: <https://github.com/rtyler>
>   Chatter: <https://twitter.com/agentdero>
>
>   % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F
> ------------------------------------------------------
>
-- 
James Dumay
Product Manager
CloudBees, Inc.
Skype: jdumaycb Twitter: i386
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.jenkins-ci.org/pipermail/jenkins-infra/attachments/20160624/17ce664f/attachment.html>


More information about the Jenkins-infra mailing list