[ovs-dev] [PATCH RFC] github-ci: Enable github actions.
Flavio Leitner
fbl at sysclose.org
Thu Mar 19 21:29:39 UTC 2020
On Tue, Mar 17, 2020 at 01:27:13PM -0700, William Tu wrote:
> So far we only use travis to do run 'make check' per commit.
> This enables per-commit check for 'make check-system-userspace' test.
> We can think about what others to add using github actions.
>
> Example run:
> https://github.com/williamtu/ovs-travis/runs/514822181?check_suite_focus=true
I like the idea, but not sure if make check-system-userspace works
well in travis environment. I mean, first it should pass or it will
just create noise there. The second thing is to be stable, or we
will see random unrelated failures in new commits.
fbl
>
> Signed-off-by: William Tu <u9012063 at gmail.com>
> ---
> .github/workflows/ovs.yml | 25 +++++++++++++++++++++++++
> Makefile.am | 1 +
> 2 files changed, 26 insertions(+)
> create mode 100644 .github/workflows/ovs.yml
>
> diff --git a/.github/workflows/ovs.yml b/.github/workflows/ovs.yml
> new file mode 100644
> index 000000000000..1e056aceed2c
> --- /dev/null
> +++ b/.github/workflows/ovs.yml
> @@ -0,0 +1,25 @@
> +name: OVS CI
> +
> +on:
> + push:
> + branches: [ master ]
> + pull_request:
> + branches: [ master ]
> +
> +jobs:
> + build:
> + runs-on: ubuntu-latest
> + steps:
> + - uses: actions/checkout at v2
> + - name: configure
> + run: ./boot.sh; ./configure
> + - name: make
> + run: make -j2
> + - name: check-system-userspace
> + run: sudo make check-system-userspace TESTSUITEFLAGS='1-30' RECHECK=yes
> + - name: Upload artifact
> + uses: actions/upload-artifact at v1.0.0
> + if: failure()
> + with:
> + name: system-userspace
> + path: tests/system-userspace-testsuite.dir/
> diff --git a/Makefile.am b/Makefile.am
> index b279303d186c..80448d0c31c1 100644
> --- a/Makefile.am
> +++ b/Makefile.am
> @@ -92,6 +92,7 @@ EXTRA_DIST = \
> $(MAN_ROOTS) \
> Vagrantfile \
> Vagrantfile-FreeBSD \
> + .github/workflows/ovs.yml \
> .mailmap
> bin_PROGRAMS =
> sbin_PROGRAMS =
> --
> 2.7.4
>
--
fbl
More information about the dev
mailing list