[v5,0/2] Introduce travis support

Message ID 20190207220114.8020-1-msantana@redhat.com
Headers show
Series
  • Introduce travis support
Related show

Message

Michael Santana Feb. 7, 2019, 10:01 p.m.
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

Comments

Michael Santana Feb. 14, 2019, 2:30 p.m. | #1
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
>
Aaron Conole Feb. 25, 2019, 6:40 p.m. | #2
Michael Santana <msantana@redhat.com> writes:

> 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

Ping?