DPDK CI discussions
 help / color / mirror / Atom feed
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: Re: [PATCH v3 0/2] Reduced checks API usage
Date: Tue, 23 Jan 2024 08:46:42 -0500	[thread overview]
Message-ID: <f7tede85fi5.fsf@redhat.com> (raw)
In-Reply-To: <20240122234034.3883647-1-aconole@redhat.com> (Aaron Conole's message of "Mon, 22 Jan 2024 18:40:32 -0500")

Aaron Conole <aconole@redhat.com> writes:

> 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

Series applied.

Thanks Ilya and Michael for quick turnaround for reviews.


      parent reply	other threads:[~2024-01-23 13:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-22 23:40 Aaron Conole
2024-01-22 23:40 ` [PATCH v3 1/2] treewide: Add a User Agent for CURL requests Aaron Conole
2024-01-23 10:47   ` Ilya Maximets
2024-01-22 23:40 ` [PATCH v3 2/2] post_pw: Store submitted checks locally as well Aaron Conole
2024-01-23  5:49   ` Michael Santana
2024-01-23 10:49   ` Ilya Maximets
2024-01-23 13:46 ` Aaron Conole [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=f7tede85fi5.fsf@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).