DPDK patches and discussions
 help / color / mirror / Atom feed
From: Michael Santana Francisco <msantana@redhat.com>
To: dev@dpdk.org
Cc: Aaron Conole <aconole@redhat.com>,
	Bruce Richardson <bruce.richardson@intel.com>,
	Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>,
	Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-dev] [PATCH v5 0/2] Introduce travis support
Date: Thu, 14 Feb 2019 09:30:57 -0500	[thread overview]
Message-ID: <a018e49b-60c7-fbaf-6411-a247971e9dfd@redhat.com> (raw)
In-Reply-To: <20190207220114.8020-1-msantana@redhat.com>

On 2/7/19 5:01 PM, Michael Santana wrote:
ping
> This series introduces the ability for any github mirrors of the DPDK
> project, including developer mirrors, to kick off builds under the
> travis CI infrastructure.  For now, this just means compilation - no
> other kinds of automated run exists yet.  In the future, this can be
> expanded to execute and report results for any test-suites that might
> exist.
>
> The series includes support for both the 'classic make' style builds
> (which are set to be deprecated at some undetermined point in the future),
> as well as the modern meson+ninja build system.  Additionally, there
> is support for building the ARM64 target with both the meson and make
> systems.
>
> The files added under .ci/ exist so that in the future, other CI support
> platforms (such as cirrus, appveyor, etc.) could have a common place to
> put their requisite scripts without polluting the main tree.
>
> Some documentation is updated, making developers aware of the new
> travis integration.
>
> The integration can also be included on the official DPDK mirror.  Build
> reports can be enabled by subscribing the travis build email to the
> test-reports mailing list (this can be done independent of this
> series being applied).
>
> v4->v5:
>    - Renamed ARM64 to AARCH64.
>
> v3->v4:
>    - Remove non-existing file form maintainers list:
>      meson_cross_aarch64_gcc.txt
>    - Renamed ARM64 to AARCH64 for travis environment variable
>
> v2->v3:
>    - Removed duplicate file meson_cross_aarch64_gcc.txt. Used
>      arm64_armv8_linuxapp_gcc file instead
>    - Renamed ambiguous variable names and comments, including the variable
>      KERNEL to DISABLE_KERNEL_MODULES and comment 'source for python' to
>      'Repo for python'
>    - Removed an already-defined variable
>
> v1 -> v2:
>    - Added patch 1/2, "examples/vhost_scsi: don't build..."
>    - Included arm64 builds
>    - Included multiple meson+ninja builds (full library, minimal library)
>    - Included multiple 'classic make' builds
>
> Aaron Conole (1):
>    examples/vhost_scsi: Don't build without virtio_scsi.h
>
> Michael Santana (1):
>    ci: Introduce travis builds for github repositories
>
>   .ci/linux-build.sh                  |  88 +++++++++++++++
>   .ci/linux-setup.sh                  |  31 ++++++
>   .travis.yml                         | 159 ++++++++++++++++++++++++++++
>   MAINTAINERS                         |   6 ++
>   doc/guides/contributing/patches.rst |   4 +
>   examples/vhost_scsi/meson.build     |   5 +
>   6 files changed, 293 insertions(+)
>   create mode 100755 .ci/linux-build.sh
>   create mode 100755 .ci/linux-setup.sh
>   create mode 100644 .travis.yml
>

  parent reply	other threads:[~2019-02-14 14:31 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-23 22:07 [dpdk-dev] [PATCH] Introduce travis builds for github repositories Michael Santana
2019-01-24  9:35 ` Bruce Richardson
2019-01-24  9:41   ` Bruce Richardson
2019-01-24 18:11   ` Aaron Conole
2019-01-24 18:31     ` Bruce Richardson
2019-01-24 18:18 ` Thomas Monjalon
2019-01-24 20:02   ` Aaron Conole
2019-01-24 19:26 ` Honnappa Nagarahalli
2019-01-24 19:51   ` Michael Santana Francisco
2019-01-30 22:16 ` [dpdk-dev] [PATCH v2 0/2] Introduce travis support Michael Santana
2019-01-30 22:16   ` [dpdk-dev] [PATCH v2 1/2] examples/vhost_scsi: Don't build without virtio_scsi.h Michael Santana
2019-01-31  9:15     ` Bruce Richardson
2019-01-30 22:16   ` [dpdk-dev] [PATCH v2 2/2] ci: Introduce travis builds for github repositories Michael Santana
2019-01-31  9:25     ` Bruce Richardson
2019-01-31 16:43       ` Aaron Conole
2019-01-31 20:32         ` Bruce Richardson
2019-01-31 20:43           ` Aaron Conole
2019-02-01 16:48   ` [dpdk-dev] [PATCH v3 0/2] Introduce travis support Michael Santana
2019-02-01 16:48     ` [dpdk-dev] [PATCH v3 1/2] examples/vhost_scsi: Don't build without virtio_scsi.h Michael Santana
2019-02-01 16:48     ` [dpdk-dev] [PATCH v3 2/2] ci: Introduce travis builds for github repositories Michael Santana
2019-02-04  9:41       ` Bruce Richardson
2019-02-06 19:17       ` Honnappa Nagarahalli
2019-02-06 20:18         ` Aaron Conole
2019-02-06 22:13     ` [dpdk-dev] [PATCH v4 0/2] Introduce travis support Michael Santana
2019-02-06 22:13       ` [dpdk-dev] [PATCH v4 1/2] examples/vhost_scsi: Don't build without virtio_scsi.h Michael Santana
2019-02-06 22:13       ` [dpdk-dev] [PATCH v4 2/2] ci: Introduce travis builds for github repositories Michael Santana
2019-02-07 17:16         ` Honnappa Nagarahalli
2019-02-07 22:01       ` [dpdk-dev] [PATCH v5 0/2] Introduce travis support Michael Santana
2019-02-07 22:01         ` [dpdk-dev] [PATCH v5 1/2] examples/vhost_scsi: Don't build without virtio_scsi.h Michael Santana
2019-02-27 14:09           ` Thomas Monjalon
2019-02-07 22:01         ` [dpdk-dev] [PATCH v5 2/2] ci: Introduce travis builds for github repositories Michael Santana
2019-02-27 13:56           ` Thomas Monjalon
2019-02-27 14:35             ` Aaron Conole
2019-02-27 15:23               ` Thomas Monjalon
2019-02-27 15:53                 ` Aaron Conole
2019-02-27 16:06                   ` Luca Boccassi
2019-02-27 16:17                     ` Aaron Conole
2019-02-14 14:30         ` Michael Santana Francisco [this message]
2019-02-25 18:40         ` [dpdk-dev] [PATCH v5 0/2] Introduce travis support Aaron Conole
2019-03-04 16:12         ` [dpdk-dev] [PATCH v6 0/1] " Michael Santana
2019-03-04 16:12           ` [dpdk-dev] [PATCH v6 1/1] ci: Introduce travis builds for github repositories Michael Santana
2019-03-04 18:14             ` Luca Boccassi
2019-03-14 13:21               ` Michael Santana Francisco
2019-03-14 13:21                 ` Michael Santana Francisco
2019-03-20 16:01             ` Thomas Monjalon
2019-03-20 16:01               ` Thomas Monjalon
2019-03-20 19:28               ` Michael Santana Francisco
2019-03-20 19:28                 ` Michael Santana Francisco
2019-03-20 21:11                 ` Luca Boccassi
2019-03-20 21:11                   ` Luca Boccassi
2019-03-21 15:45                   ` Michael Santana Francisco
2019-03-21 15:45                     ` Michael Santana Francisco
2019-03-22 16:56             ` [dpdk-dev] [PATCH v7] " Michael Santana
2019-03-22 16:56               ` Michael Santana
2019-03-25 15:32               ` [dpdk-dev] [PATCH v8] " Michael Santana
2019-03-25 15:32                 ` Michael Santana
2019-03-25 16:10                 ` Thomas Monjalon
2019-03-25 16:10                   ` Thomas Monjalon
2019-03-26 21:54                   ` Thomas Monjalon
2019-03-26 21:54                     ` Thomas Monjalon

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=a018e49b-60c7-fbaf-6411-a247971e9dfd@redhat.com \
    --to=msantana@redhat.com \
    --cc=Honnappa.Nagarahalli@arm.com \
    --cc=aconole@redhat.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).