It is not sustainable to keep supporting Travis CI when our maintainer
have exhausted their free CI credit allowance and it isn't easily
renewable for most

While there are still some unique scenarios covered by Travis, this is
not useful when maintainers can't run the pipelines.  If people see
scenarios that are desirable for GitLab CI they can be added as jobs
when desired.

Daniel P. Berrangé (2):
  tests/docker: remove travis container
  travis: remove travis configuration and all references to Travis CI

 .travis.yml                            | 439 -------------------------
 MAINTAINERS                            |   3 -
 configure                              |   1 -
 contrib/gitdm/filetypes.txt            |   2 +-
 docs/devel/testing.rst                 |  14 -
 scripts/travis/coverage-summary.sh     |  27 --
 tests/docker/Makefile.include          |  11 +-
 tests/docker/docker.py                 |   2 +-
 tests/docker/dockerfiles/travis.docker |  17 -
 tests/docker/travis                    |  22 --
 tests/docker/travis.py                 |  47 ---
 tests/qemu-iotests/079                 |   2 +-
 tests/test-util-filemonitor.c          |  11 -
 13 files changed, 5 insertions(+), 593 deletions(-)
 delete mode 100644 .travis.yml
 delete mode 100755 scripts/travis/coverage-summary.sh
 delete mode 100644 tests/docker/dockerfiles/travis.docker
 delete mode 100755 tests/docker/travis
 delete mode 100755 tests/docker/travis.py

-- 
2.29.2