From: Aaron Conole <aconole@redhat.com>
To: Adam Hassick <ahassick@iol.unh.edu>
Cc: ci@dpdk.org
Subject: Re: [PATCH v3 0/3] Add a script to create series artifacts
Date: Thu, 22 Feb 2024 14:25:40 -0500 [thread overview]
Message-ID: <f7tv86gcnd7.fsf@redhat.com> (raw)
In-Reply-To: <20240118234120.29256-1-ahassick@iol.unh.edu> (Adam Hassick's message of "Thu, 18 Jan 2024 18:41:17 -0500")
Adam Hassick <ahassick@iol.unh.edu> writes:
> The process of applying patches and bundling the source code into an
> archive varies across testing labs. Historically, the process for
> applying patches at the Community Lab was not visible to the broader
> community and was inextricable from lab infrastructure. The new script
> introduced in this patch aims to resolve these issues. This script is
> intended to serve as a reference process for creating series artifacts.
> A "series artifact" is an archive containing a copy of the DPDK source
> code with a patch series applied. We perform a test build prior to
> creating the archive as well. At the Community Lab, these archives are
> used for all of our tests. At the time of writing, this script is being
> used in production.
>
> The script depends on the "pw_maintainers_cli" and patch parser scripts
> in the CI repository. It also depends on pygit2 for managing the DPDK
> repository, pyyaml for parsing the configuration file, and git_pw for
> pulling in the series as a patch file.
>
> This script does not implement handling of the dependency labels. There
> is an ongoing effort to get this implemented into Patchwork as a
> feature.
> ---
Marged - thanks!
prev parent reply other threads:[~2024-02-22 19:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-18 23:41 Adam Hassick
2024-01-18 23:41 ` [PATCH v3 1/3] tools: Add script to create artifacts Adam Hassick
2024-01-18 23:41 ` [PATCH v3 2/3] config: Add example config file Adam Hassick
2024-01-18 23:41 ` [PATCH v3 3/3] doc: Add documentation Adam Hassick
2024-02-22 19:25 ` 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=f7tv86gcnd7.fsf@redhat.com \
--to=aconole@redhat.com \
--cc=ahassick@iol.unh.edu \
--cc=ci@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 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).