From: Aaron Conole <aconole@redhat.com>
To: ci@dpdk.org
Cc: Michael Santana <msantana@redhat.com>,
Ilya Maximets <i.maximets@ovn.org>, Jeremy Kerr <jk@ozlabs.org>
Subject: [PATCH v2 0/2] Reduced checks API usage
Date: Mon, 22 Jan 2024 14:32:30 -0500 [thread overview]
Message-ID: <20240122193232.3734371-1-aconole@redhat.com> (raw)
As Jeremy Kerr reports, we aren't being as nice as we should be w.r.t.
API usage - especially around the checks API reporting. While the
initial version *worked* for what we wanted, we are heavily using the
checks API, especially when we don't need to be.
This series should reduce the number of API calls we make into
patchwork with respect to the checks API specifically.
Additionally, we add a simple token to identify that the requests
coming in are from a patchwork robot project (so at least a site
admin can start identifying who is actually sending the requests).
Aaron Conole (2):
treewide: Add a User Agent for CURL requests
post_pw: Store submitted checks locally as well
ci_mon | 2 +-
github_get_logs.sh | 8 ++++----
github_mon | 2 +-
github_restart | 6 ++++--
jenkins_lib.sh | 5 +++--
post_pw.sh | 46 +++++++++++++++++++++++++++++++++++++++++-----
pw_mon | 14 +++++++-------
series_db_lib.sh | 25 +++++++++++++++++++++++++
8 files changed, 86 insertions(+), 22 deletions(-)
--
2.41.0
next reply other threads:[~2024-01-22 19:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-22 19:32 Aaron Conole [this message]
2024-01-22 19:32 ` [PATCH v2 1/2] treewide: Add a User Agent for CURL requests Aaron Conole
2024-01-22 19:32 ` [PATCH v2 2/2] post_pw: Store submitted checks locally as well Aaron Conole
2024-01-22 20:39 ` Michael Santana
2024-01-22 23:14 ` Aaron Conole
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=20240122193232.3734371-1-aconole@redhat.com \
--to=aconole@redhat.com \
--cc=ci@dpdk.org \
--cc=i.maximets@ovn.org \
--cc=jk@ozlabs.org \
--cc=msantana@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).