DPDK CI discussions
 help / color / mirror / Atom feed
From: Adam Hassick <ahassick@iol.unh.edu>
To: ci@dpdk.org
Cc: aconole@redhat.com, alialnu@nvidia.com,
	Adam Hassick <ahassick@iol.unh.edu>
Subject: [PATCH 0/2] Add a script to create series artifacts
Date: Wed, 10 Jan 2024 09:57:13 -0500	[thread overview]
Message-ID: <20240110145715.28157-1-ahassick@iol.unh.edu> (raw)

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 and pyyaml for parsing the configuration file.

This script does not implement handling of the dependency labels. There
is an ongoing effort to get this implemented into Patchwork as a


* Add script to create artifacts
* Add example config file

Adam Hassick (2):
  tools: Add script to create artifacts
  config: Add example config file

 config/artifacts.yml            |  22 ++
 tools/create_series_artifact.py | 453 ++++++++++++++++++++++++++++++++
 2 files changed, 475 insertions(+)
 create mode 100644 config/artifacts.yml
 create mode 100755 tools/create_series_artifact.py


             reply	other threads:[~2024-01-10 14:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-10 14:57 Adam Hassick [this message]
2024-01-10 14:57 ` [PATCH 1/2] tools: Add script to create artifacts Adam Hassick
2024-01-10 16:54   ` Aaron Conole
2024-01-10 18:56     ` Patrick Robb
     [not found]     ` <CAC-YWqhfQAPQ2=yaqpgG+axPSG9n=kScJULkYv9ZybTnSiZUog@mail.gmail.com>
2024-01-16 14:10       ` Aaron Conole
2024-01-16 23:41         ` Adam Hassick
2024-01-11 11:55   ` Juraj Linkeš
2024-01-10 14:57 ` [PATCH 2/2] config: Add example config file 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=20240110145715.28157-1-ahassick@iol.unh.edu \
    --to=ahassick@iol.unh.edu \
    --cc=aconole@redhat.com \
    --cc=alialnu@nvidia.com \
    --cc=ci@dpdk.org \


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