From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Cc: ajit.khaparde@broadcom.com, alialnu@mellanox.com
Subject: [dpdk-dev] reenchanting bugzilla with REST commands
Date: Sun, 26 Apr 2020 17:25:56 +0200 [thread overview]
Message-ID: <3483381.tlMGI8NQbM@thomas> (raw)
Hi,
There are 144 bugs open in
https://bugs.dpdk.org/buglist.cgi?bug_status=__open__&product=DPDK
Some regular effort is required to follow and update the bugs.
If you don't have a bugzilla account on dpdk.org, please go to
https://bugs.dpdk.org/createaccount.cgi
In case it could motivate some of us using bugzilla more regularly,
please be aware a REST API is available in bugzilla.
The API documentation is quite good:
https://bugzilla.readthedocs.io/en/latest/api/
For user-authenticated calls, a secret key can be generated at
https://bugs.dpdk.org/userprefs.cgi?tab=apikey
-- example --
Below is a shell command getting (and formatting) not assigned bugs:
curl -s 'https://bugs.dpdk.org/rest/bug?product=DPDK&status=UNCONFIRMED&status=CONFIRMED&status=IN_PROGRESS&include_fields=id,summary&assigned_to=dev@dpdk.org' | tr -d '"' | sed -e 's,^{bugs:\[{,,' -e 's,}]}$,,' -e 's/},{/\n/g' | sed -e 's/,id:/\n=/' -e 's/^id:\([0-9]*\),\(.*\)/\2\n=\1/' | sed -e 's,^=,\thttps://bugs.dpdk.org/show_bug.cgi?id=,' -e 's,^summary:,,'
reply other threads:[~2020-04-26 15:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3483381.tlMGI8NQbM@thomas \
--to=thomas@monjalon.net \
--cc=ajit.khaparde@broadcom.com \
--cc=alialnu@mellanox.com \
--cc=dev@dpdk.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.