ci: drop Travis configuration
PATCH 1/1 ci: drop Travis configuration
We stopped using Travis in the main branch and in the public CI in favor of GHA more than a year ago.
The UNH community lab now covers testing native compilation and unit tests for ARM platforms.
We decided to stop maintaining the configuration in our repository with the argument that "if it is not tested, it is broken".
--- .ci/linux-build.sh | 19 --- .travis.yml | 172 ---------------------------- MAINTAINERS | 1 - devtools/check-spdx-tag.sh | 2 +- doc/guides/contributing/patches.rst | 4 - 5 files changed, 1 insertion(+), 197 deletions(-) delete mode 100644 .travis.yml
.ci/linux-build.sh +0 -19
@@ -9,25 +9,6 @@ fi # Builds are run as root in containers, no need for sudo [ "$(id -u)" != '0' ] || alias sudo= -on_error() { - if [ $? = 0 ]; then - exit - fi - FILES_TO_PRINT="build/meson-logs/testlog.txt" - FILES_TO_PRINT="$FILES_TO_PRINT build/.ninja_log" - FILES_TO_PRINT="$FILES_TO_PRINT build/meson-logs/meson-log.txt" - FILES_TO_PRINT="$FILES_TO_PRINT build/gdb.log" - - for pr_file in $FILES_TO_PRINT; do - if [ -e "$pr_file" ]; then - cat "$pr_file" - fi - done -} -# We capture the error logs as artifacts in Github Actions, no need to dump -# them via a EXIT handler. -[ -n "$GITHUB_WORKFLOW" ] || trap on_error EXIT - install_libabigail() { version=$1 instdir=$2
.travis.yml deleted +0 -172
172 lines not on this page · raw message
MAINTAINERS +0 -1
@@ -131,7 +131,6 @@ F: devtools/check-meson.py Public CI M: Aaron Conole <[email protected]> M: Michael Santana <[email protected]> -F: .travis.yml F: .github/workflows/build.yml F: .ci/
devtools/check-spdx-tag.sh +1 -1
@@ -20,7 +20,7 @@ check_spdx() { echo "--------------------------" fi git grep -L SPDX-License-Identifier -- \ - ':^.git*' ':^.mailmap' ':^.ci/*' ':^.travis.yml' \ + ':^.git*' ':^.mailmap' ':^.ci/*' \ ':^README' ':^MAINTAINERS' ':^VERSION' ':^ABI_VERSION' \ ':^*/Kbuild' ':^*/README' \ ':^license/' ':^config/' ':^buildtools/' ':^*/poetry.lock' \
doc/guides/contributing/patches.rst +0 -4
@@ -35,10 +35,6 @@ It is also worth registering for the DPDK `Patchwork <https://patches.dpdk.org/p 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 <http://www.git-scm.com/book/>`_ for further information.
Signature · 1 line
2.38.1
Quoted 9 lines · David Marchand
We stopped using Travis in the main branch and in the public CI in favor of GHA more than a year ago.
The UNH community lab now covers testing native compilation and unit tests for ARM platforms.We decided to stop maintaining the configuration in our repository with the argument that "if it is not tested, it is broken".
Signed-off-by David Marchand <[email protected]>
Quoted 10 lines · David Marchand
We stopped using Travis in the main branch and in the public CI in favor of GHA more than a year ago.
The UNH community lab now covers testing native compilation and unit tests for ARM platforms.We decided to stop maintaining the configuration in our repository with the argument that "if it is not tested, it is broken".
Signed-off-by David Marchand <[email protected]>---
David Marchand
AppliedQuoted 8 lines · Aaron Conole
Quoted 5 lines · David Marchand
We stopped using Travis in the main branch and in the public CI in favor of GHA more than a year ago.
The UNH community lab now covers testing native compilation and unit tests for ARM platforms.
Quoted 5 lines
Quoted 4 lines
We decided to stop maintaining the configuration in our repository with the argument that "if it is not tested, it is broken".
Signed-off-by David Marchand <[email protected]>Acked-by Aaron Conole <[email protected]>
Applied, thanks.
Signature · 1 line
David Marchand