From: Martin Jansa <martin.jansa@gmail.com>
To: "João Henrique Ferreira de Freitas" <joaohf@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/2] reporter-error sending report
Date: Thu, 13 Nov 2014 13:58:52 +0100 [thread overview]
Message-ID: <20141113125852.GA2456@jama> (raw)
In-Reply-To: <1415833719-6255-1-git-send-email-joaohf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1948 bytes --]
On Wed, Nov 12, 2014 at 09:08:37PM -0200, João Henrique Ferreira de Freitas wrote:
> When the Error Reporting Tool is enabled and the build fails, then the report-error
> prints an url that the user needs to get and use the send-error-report tool which
> will sends the reporter to a public or private reporting server error.
>
> This works very well if the user is sitting in front of the building machine.
> There are some cases, like jobs running on Jenkins server, that need to send
> reports automatically when a build fails.
>
> This patch set introduces a glue between reporter-error.bbclass and send-error-reporter tool.
it's report-error.bbclass and send-error-report (not reporter)
> So, report erros will be send as soon as an error happens.
>
> Two new variables were added and the user takes the responsible to fill them (conf/site.conf),
> for example:
>
> INHERIT += "report-error"
> ERR_REPORT_SERVER = "127.0.0.1:8000"
> ERR_REPORT_USER = "joaohf"
> ERR_REPORT_EMAIL = "joaohf@gmail.com"
See
http://lists.openembedded.org/pipermail/openembedded-core/2014-March/090576.html
which does the same, but was rejected because of concerns that someone
will unintentionally upload sensitive data to some public report server.
>
>
> João Henrique Ferreira de Freitas (2):
> report-error: sending error report to server without user intervention
> report-error: send report error with username and email
>
> meta/classes/report-error.bbclass | 15 +++++++++++++
> scripts/send-error-report | 45 ++++++++++++++++++++++++---------------
> 2 files changed, 43 insertions(+), 17 deletions(-)
>
> --
> 1.9.1
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
prev parent reply other threads:[~2014-11-13 12:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-12 23:08 [PATCH 0/2] reporter-error sending report João Henrique Ferreira de Freitas
2014-11-12 23:08 ` [PATCH 1/2] report-error: sending error report to server without user intervention João Henrique Ferreira de Freitas
2014-11-12 23:08 ` [PATCH 2/2] report-error: send report error with username and email João Henrique Ferreira de Freitas
2014-11-13 12:58 ` Martin Jansa [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20141113125852.GA2456@jama \
--to=martin.jansa@gmail.com \
--cc=joaohf@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox