DPDK CI discussions
 help / color / mirror / Atom feed
From: Ali Alnubani <alialnu@nvidia.com>
To: Adam Hassick <ahassick@iol.unh.edu>, "ci@dpdk.org" <ci@dpdk.org>
Cc: "aconole@redhat.com" <aconole@redhat.com>
Subject: RE: [PATCH v7 6/6] containers/Makefile: Makefile to automate builds
Date: Wed, 12 Jul 2023 11:43:31 +0000	[thread overview]
Message-ID: <DM4PR12MB5167C8EE2277B7FB3023497CDA36A@DM4PR12MB5167.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20230711202124.1636317-7-ahassick@iol.unh.edu>

> -----Original Message-----
> From: Adam Hassick <ahassick@iol.unh.edu>
> Sent: Tuesday, July 11, 2023 11:21 PM
> To: ci@dpdk.org
> Cc: Ali Alnubani <alialnu@nvidia.com>; aconole@redhat.com; Adam Hassick
> <ahassick@iol.unh.edu>
> Subject: [PATCH v7 6/6] containers/Makefile: Makefile to automate builds
> 
> From: Owen Hilyard <ohilyard at iol.unh.edu>
> 
> The Makefile that can be used to build all of the container images using
> "make build", and can also be used to push them to a remote repository
> (for use in CI).
> 
> Signed-off-by: Owen Hilyard <ohilyard at iol.unh.edu>
> Signed-off-by: Adam Hassick <ahassick@iol.unh.edu>
> ---
>  containers/Makefile | 250
> ++++++++++++++++++++++++++++++++++++++++++++
>  1 file changed, 250 insertions(+)
>  create mode 100644 containers/Makefile
> 
> diff --git a/containers/Makefile b/containers/Makefile
> new file mode 100644
> index 0000000..5904821
> --- /dev/null
> +++ b/containers/Makefile
> @@ -0,0 +1,250 @@
[..]
> +# Copy the Coveirty Scan binaries from a source into the context directory.

s/Coveirty/Coverity/

  reply	other threads:[~2023-07-12 11:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-11 20:21 [PATCH v7 0/6] Community Lab Containers and Builder Engine Adam Hassick
2023-07-11 20:21 ` [PATCH v7 1/6] containers/docs: Add container builder start Adam Hassick
2023-07-12 11:43   ` Ali Alnubani
2023-07-11 20:21 ` [PATCH v7 2/6] containers/inventory: Add inventory for container builder Adam Hassick
2023-07-11 20:21 ` [PATCH v7 3/6] containers/builder: Dockerfile creation script Adam Hassick
2023-07-11 20:21 ` [PATCH v7 4/6] containers/templates: Templates for Dockerfiles Adam Hassick
2023-07-11 20:21 ` [PATCH v7 5/6] containers/container_builder: Container for python scripts Adam Hassick
2023-07-11 20:21 ` [PATCH v7 6/6] containers/Makefile: Makefile to automate builds Adam Hassick
2023-07-12 11:43   ` Ali Alnubani [this message]
2023-07-12 11:45 ` [PATCH v7 0/6] Community Lab Containers and Builder Engine Ali Alnubani
2023-07-17 19:07 ` Aaron Conole
2023-07-18 13:40   ` Adam Hassick
2023-07-18 14:17     ` 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=DM4PR12MB5167C8EE2277B7FB3023497CDA36A@DM4PR12MB5167.namprd12.prod.outlook.com \
    --to=alialnu@nvidia.com \
    --cc=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).