[ovs-dev] [PATCH branch-2.9 2/2] travis: Remove support for Travis CI.
Ilya Maximets
i.maximets at ovn.org
Thu Nov 26 12:49:22 UTC 2020
All CI jobs are covered by GitHub Actions now.
What happened to Travis CI:
https://mail.openvswitch.org/pipermail/ovs-dev/2020-November/377773.html
Signed-off-by: Ilya Maximets <i.maximets at ovn.org>
---
.travis.yml | 52 -------------------
.../contributing/submitting-patches.rst | 7 ++-
Documentation/topics/testing.rst | 44 +++-------------
Makefile.am | 1 -
README.rst | 2 -
5 files changed, 11 insertions(+), 95 deletions(-)
delete mode 100644 .travis.yml
diff --git a/.travis.yml b/.travis.yml
deleted file mode 100644
index 6eba3ebfc..000000000
--- a/.travis.yml
+++ /dev/null
@@ -1,52 +0,0 @@
-language: c
-compiler:
- - gcc
- - clang
-
-os:
- - linux
-
-addons:
- apt:
- packages:
- - bc
- - gcc-multilib
- - libssl-dev
- - llvm-dev
- - libjemalloc1
- - libjemalloc-dev
- - libnuma-dev
- - python-sphinx
- - libelf-dev
-
-before_install: ./.ci/${TRAVIS_OS_NAME}-prepare.sh
-
-before_script: export PATH=$PATH:$HOME/bin
-
-env:
- - OPTS="--disable-ssl"
- - TESTSUITE=1 KERNEL=3.16.54
- - TESTSUITE=1 OPTS="--enable-shared"
- - BUILD_ENV="-m32" OPTS="--disable-ssl"
- - KERNEL=3.16.54 DPDK=1
- - KERNEL=3.16.54 DPDK=1 OPTS="--enable-shared"
- - KERNEL=4.15.3
- - KERNEL=4.14.19
- - KERNEL=4.9.149
- - KERNEL=4.4.115
- - KERNEL=4.1.49
- - KERNEL=3.10.108
- - TESTSUITE=1 LIBS=-ljemalloc
-
-matrix:
- include:
- - os: osx
- compiler: clang
- env: OPTS="--disable-ssl"
-
-script: ./.ci/${TRAVIS_OS_NAME}-build.sh $OPTS
-
-notifications:
- email:
- recipients:
- - ovs-build at openvswitch.org
diff --git a/Documentation/internals/contributing/submitting-patches.rst b/Documentation/internals/contributing/submitting-patches.rst
index 0f57b6a9d..5ce65a484 100644
--- a/Documentation/internals/contributing/submitting-patches.rst
+++ b/Documentation/internals/contributing/submitting-patches.rst
@@ -68,10 +68,9 @@ Testing is also important:
feature. A bug fix patch should preferably add a test that would
fail if the bug recurs.
-If you are using GitHub, then you may utilize the travis-ci.org and the GitHub
-Actions CI build systems. They will run some of the above tests automatically
-when you push changes to your repository. See the "Continuous Integration with
-Travis-CI" in :doc:`/topics/testing` for details on how to set it up.
+If you are using GitHub, then you may utilize the GitHub Actions CI build
+system. It will run some of the above tests automatically when you push
+changes to your repository.
Email Subject
-------------
diff --git a/Documentation/topics/testing.rst b/Documentation/topics/testing.rst
index a49336b79..607d8caed 100644
--- a/Documentation/topics/testing.rst
+++ b/Documentation/topics/testing.rst
@@ -341,45 +341,17 @@ You should invoke scan-view to view analysis results. The last line of output
from ``clang-analyze`` will list the command (containing results directory)
that you should invoke to view the results on a browser.
-Continuous Integration with Travis CI
--------------------------------------
+Continuous Integration with GitHub Actions
+------------------------------------------
-A .travis.yml file is provided to automatically build Open vSwitch with various
-build configurations and run the testsuite using Travis CI. Builds will be
-performed with gcc, sparse and clang with the -Werror compiler flag included,
-therefore the build will fail if a new warning has been introduced.
+A ``.github/workflows/*.yml`` files provided to automatically build
+Open vSwitch with various build configurations and run the testsuite using
+GitHub Actions. Builds will be performed with gcc, sparse and clang with the
+-Werror compiler flag included, therefore the build will fail if a new warning
+has been introduced.
The CI build is triggered via git push (regardless of the specific branch) or
-pull request against any Open vSwitch GitHub repository that is linked to
-travis-ci.
-
-Instructions to setup travis-ci for your GitHub repository:
-
-1. Go to https://travis-ci.org/ and sign in using your GitHub ID.
-2. Go to the "Repositories" tab and enable the ovs repository. You may disable
- builds for pushes or pull requests.
-3. In order to avoid forks sending build failures to the upstream mailing list,
- the notification email recipient is encrypted. If you want to receive email
- notification for build failures, replace the the encrypted string:
-
- 1. Install the travis-ci CLI (Requires ruby >=2.0): gem install travis
- 2. In your Open vSwitch repository: travis encrypt mylist at mydomain.org
- 3. Add/replace the notifications section in .travis.yml and fill in the
- secure string as returned by travis encrypt::
-
- notifications:
- email:
- recipients:
- - secure: "....."
-
- .. note::
- You may remove/omit the notifications section to fall back to default
- notification behaviour which is to send an email directly to the author and
- committer of the failing commit. Note that the email is only sent if the
- author/committer have commit rights for the particular GitHub repository.
-
-4. Pushing a commit to the repository which breaks the build or the
- testsuite will now trigger a email sent to mylist at mydomain.org
+pull request against any Open vSwitch GitHub repository.
vsperf
------
diff --git a/Makefile.am b/Makefile.am
index 833640d53..1cec215a1 100644
--- a/Makefile.am
+++ b/Makefile.am
@@ -80,7 +80,6 @@ EXTRA_DIST = \
.ci/osx-build.sh \
.ci/osx-prepare.sh \
.github/workflows/build-and-test.yml \
- .travis.yml \
appveyor.yml \
boot.sh \
$(MAN_FRAGMENTS) \
diff --git a/README.rst b/README.rst
index 9ce2646de..2075b506f 100644
--- a/README.rst
+++ b/README.rst
@@ -8,8 +8,6 @@ Open vSwitch
.. image:: https://github.com/openvswitch/ovs/workflows/Build%20and%20Test/badge.svg
:target: https://github.com/openvswitch/ovs/actions
-.. image:: https://travis-ci.org/openvswitch/ovs.png
- :target: https://travis-ci.org/openvswitch/ovs
.. image:: https://ci.appveyor.com/api/projects/status/github/openvswitch/ovs?branch=master&svg=true&retina=true
:target: https://ci.appveyor.com/project/blp/ovs/history
--
2.25.4
More information about the dev
mailing list