From ce949484d165539b9a1eb04c4a5c6917d3311545 Mon Sep 17 00:00:00 2001 From: David Marchand Date: Wed, 13 Jan 2021 10:03:12 +0100 Subject: [PATCH] doc: recommend GitHub Actions for CI Update the contributing guidelines to describe GitHub Actions first and add a warning about Travis usage. Fixes: 87009585e293 ("ci: hook to GitHub Actions") Signed-off-by: David Marchand Acked-by: Aaron Conole --- doc/guides/contributing/patches.rst | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/doc/guides/contributing/patches.rst b/doc/guides/contributing/patches.rst index 4e9140bca4..6dbbd5f8d1 100644 --- a/doc/guides/contributing/patches.rst +++ b/doc/guides/contributing/patches.rst @@ -32,9 +32,12 @@ The mailing list for DPDK development is `dev@dpdk.org `_ in order to submit patches. It is also worth registering for the DPDK `Patchwork `_ -If you are using the GitHub service, you can link your repository to -the ``travis-ci.org`` build service. When you push patches to your GitHub -repository, the travis service will automatically build your changes. +If you are using the GitHub service, pushing to a branch will trigger GitHub +Actions to automatically build your changes and run unit tests and ABI checks. + +Additionally, a Travis configuration is available in DPDK but Travis free usage +is limited to a few builds. +You can link your repository to the ``travis-ci.com`` build service. The development process requires some familiarity with the ``git`` version control system. Refer to the `Pro Git Book `_ for further information. -- 2.20.1