DPDK CI discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Patrick Robb <probb@iol.unh.edu>, ci@dpdk.org
Cc: dev@dpdk.org,
	"NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>,
	David Marchand <david.marchand@redhat.com>,
	Aaron Conole <aconole@redhat.com>, zhoumin <zhoumin@loongson.cn>,
	"Mcnamara, John" <john.mcnamara@intel.com>,
	Adam Hassick <ahassick@iol.unh.edu>
Subject: Re: Depends-on patchseries support via git-pw or patchwork
Date: Mon, 8 Jan 2024 16:18:44 +0000	[thread overview]
Message-ID: <76c7821a-f7b9-4782-8c7f-af726da203a3@amd.com> (raw)
In-Reply-To: <CAJvnSUBWjRfQrL5Hss-QwPjZG=D1cZdHAgVXO-0mDWEst+m_cg@mail.gmail.com>

On 12/22/2023 5:26 PM, Patrick Robb wrote:
> Hi all,
> As some of you know from discussions at DPDK CI meetings, Adam from UNH
> is writing a script which leverages git-pw, and takes as arguments a
> patch series patchwork id, patchwork project, and pw token, and produces
> a project artifact for CI testing purposes. Starting in January we will
> use it for applying patches to DPDK and creating our dpdk.tar.gz
> artifacts for testing. And, we will submit it to the dpdk-ci repo. 
> Anyways, when we originally discussed the idea, Thomas suggested that we
> implement the depends-on functionality by contributing to the git-pw
> project, as opposed to implementing the depend-on support in the create
> artifact script itself. Adam did create a github issue on the git-pw
> project in order to poll the community for interest in this feature, and
> one of the patchwork maintainers chimed in to suggest that rather than
> implementing the feature on the client side via git-pw, it should simply
> be implemented for patchwork itself. That way if it's patchwork server
> side and exposed via the api, other client side tools like pwclient can
> also receive the benefits.
> I just wanted to flag this on the ci mailing list so that anyone with
> thoughts could submit them on the Github issue, which you can find
> here: https://github.com/getpatchwork/git-pw/issues/71
> <https://github.com/getpatchwork/git-pw/issues/71>
> Thanks Adam for pushing this effort forward. 

Thanks Patrick for the update and thanks Adam for driving this.

Implementing support to patchwork sounds good to me, is anything
expected from our end for this?

  reply	other threads:[~2024-01-08 16:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-22 17:26 Patrick Robb
2024-01-08 16:18 ` Ferruh Yigit [this message]
2024-01-09 21:38   ` Adam Hassick

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=76c7821a-f7b9-4782-8c7f-af726da203a3@amd.com \
    --to=ferruh.yigit@amd.com \
    --cc=aconole@redhat.com \
    --cc=ahassick@iol.unh.edu \
    --cc=ci@dpdk.org \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@intel.com \
    --cc=probb@iol.unh.edu \
    --cc=thomas@monjalon.net \
    --cc=zhoumin@loongson.cn \


* 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).