travis: delete all Linux jobs

[libvirt PATCH] travis: delete all Linux jobs

Posted by Daniel P. Berrangé 4 years ago

The Fedora rawhide job started failing with the latest container build.
Since we now have broad CI coverage on GitLab CI, there's not a strong
reason to continue using Travis for Linux jobs. Deleting the redundant
jobs is a better use of time than trying to debug the failure.

Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
---
 .travis.yml | 47 -----------------------------------------------
 1 file changed, 47 deletions(-)

diff --git a/.travis.yml b/.travis.yml
index f400f76118..0548b28b01 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -18,53 +18,6 @@ addons:
 
 matrix:
   include:
-    - services:
-        - docker
-      env:
-        - IMAGE="ubuntu-1804"
-        - MAKE_ARGS="syntax-check distcheck"
-      script:
-        - make -C ci/ ci-build@$IMAGE CI_MAKE_ARGS="$MAKE_ARGS"
-    - services:
-        - docker
-      env:
-        - IMAGE="centos-7"
-        - MAKE_ARGS="syntax-check distcheck"
-      script:
-        - make -C ci/ ci-build@$IMAGE CI_MAKE_ARGS="$MAKE_ARGS"
-    - services:
-        - docker
-      env:
-        - IMAGE="debian-9"
-        - MAKE_ARGS="syntax-check distcheck"
-      script:
-        - make -C ci/ ci-build@$IMAGE CI_MAKE_ARGS="$MAKE_ARGS"
-    - services:
-        - docker
-      env:
-        - IMAGE="fedora-31"
-        - MAKE_ARGS="syntax-check distcheck"
-      script:
-        - make -C ci/ ci-build@$IMAGE CI_MAKE_ARGS="$MAKE_ARGS"
-    - services:
-        - docker
-      env:
-        - IMAGE="fedora-rawhide"
-        - MAKE_ARGS="syntax-check distcheck"
-      script:
-        - make -C ci/ ci-build@$IMAGE CI_MAKE_ARGS="$MAKE_ARGS"
-    - services:
-        - docker
-      env:
-        - IMAGE="fedora-30-cross-mingw32"
-      script:
-        - make -C ci/ ci-build@$IMAGE
-    - services:
-        - docker
-      env:
-        - IMAGE="fedora-30-cross-mingw64"
-      script:
-        - make -C ci/ ci-build@$IMAGE
     - compiler: clang
       language: c
       os: osx
-- 
2.24.1

Re: [libvirt PATCH] travis: delete all Linux jobs

Posted by Andrea Bolognani 4 years ago

On Mon, 2020-03-30 at 17:04 +0100, Daniel P. Berrangé wrote:
> The Fedora rawhide job started failing with the latest container build.
> Since we now have broad CI coverage on GitLab CI, there's not a strong
> reason to continue using Travis for Linux jobs. Deleting the redundant
> jobs is a better use of time than trying to debug the failure.

Especially since it works fine both on GitLab, using the same
container image, and even locally, using the very same build script.

  Reviewed-by: Andrea Bolognani <abologna@redhat.com>

and safe for freeze.

My only concern is that our ci/Makefile scaffolding will bitrot now
that it will no longer be exercised directly through CI... Perhaps we
could leave a single Linux job enabled on Travis CI for the sole
purpose of preventing that?

-- 
Andrea Bolognani / Red Hat / Virtualization

Re: [libvirt PATCH] travis: delete all Linux jobs

Posted by Daniel P. Berrangé 4 years ago

On Mon, Mar 30, 2020 at 07:05:26PM +0200, Andrea Bolognani wrote:
> On Mon, 2020-03-30 at 17:04 +0100, Daniel P. Berrangé wrote:
> > The Fedora rawhide job started failing with the latest container build.
> > Since we now have broad CI coverage on GitLab CI, there's not a strong
> > reason to continue using Travis for Linux jobs. Deleting the redundant
> > jobs is a better use of time than trying to debug the failure.
> 
> Especially since it works fine both on GitLab, using the same
> container image, and even locally, using the very same build script.
> 
>   Reviewed-by: Andrea Bolognani <abologna@redhat.com>
> 
> and safe for freeze.
> 
> My only concern is that our ci/Makefile scaffolding will bitrot now
> that it will no longer be exercised directly through CI... Perhaps we
> could leave a single Linux job enabled on Travis CI for the sole
> purpose of preventing that?

True, but I'd rather like to eliminate duplicate failures being reported
by Travis that we're already getting from GitLab, and thus stop loooking
at Travis as much as is possible, so if it fails we know it is macOS
related.

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|

Re: [libvirt PATCH] travis: delete all Linux jobs

Posted by Andrea Bolognani 4 years ago

On Mon, 2020-03-30 at 18:12 +0100, Daniel P. Berrangé wrote:
> On Mon, Mar 30, 2020 at 07:05:26PM +0200, Andrea Bolognani wrote:
> > My only concern is that our ci/Makefile scaffolding will bitrot now
> > that it will no longer be exercised directly through CI... Perhaps we
> > could leave a single Linux job enabled on Travis CI for the sole
> > purpose of preventing that?
> 
> True, but I'd rather like to eliminate duplicate failures being reported
> by Travis that we're already getting from GitLab, and thus stop loooking
> at Travis as much as is possible, so if it fails we know it is macOS
> related.

Since we're going to be forced to keep the macOS job on Travis, we
will still ultimately have to look in two places... Additionally,
while right now CentOS CI gives you an overview of the CI status of
all jobs, from libvirt all the way to virt-manager, once all projects
have been moved to GitLab CI we're going to lose that.

Could we create a sort of high-level CI dashboard that provides an
at-a-glance status? It doesn't have to be very detailed, it could be
basically just a single colored dot per project to signal its overall
status, along with links pointing to the appropriate pages for when
additional details are necessary.

-- 
Andrea Bolognani / Red Hat / Virtualization

Re: [libvirt PATCH] travis: delete all Linux jobs

Posted by Daniel P. Berrangé 4 years ago

On Tue, Mar 31, 2020 at 02:21:00PM +0200, Andrea Bolognani wrote:
> On Mon, 2020-03-30 at 18:12 +0100, Daniel P. Berrangé wrote:
> > On Mon, Mar 30, 2020 at 07:05:26PM +0200, Andrea Bolognani wrote:
> > > My only concern is that our ci/Makefile scaffolding will bitrot now
> > > that it will no longer be exercised directly through CI... Perhaps we
> > > could leave a single Linux job enabled on Travis CI for the sole
> > > purpose of preventing that?
> > 
> > True, but I'd rather like to eliminate duplicate failures being reported
> > by Travis that we're already getting from GitLab, and thus stop loooking
> > at Travis as much as is possible, so if it fails we know it is macOS
> > related.
> 
> Since we're going to be forced to keep the macOS job on Travis, we
> will still ultimately have to look in two places... Additionally,
> while right now CentOS CI gives you an overview of the CI status of
> all jobs, from libvirt all the way to virt-manager, once all projects
> have been moved to GitLab CI we're going to lose that.
> 
> Could we create a sort of high-level CI dashboard that provides an
> at-a-glance status? It doesn't have to be very detailed, it could be
> basically just a single colored dot per project to signal its overall
> status, along with links pointing to the appropriate pages for when
> additional details are necessary.

That's doable with a combination of GitLab CI + Pages I expect.
A script would fetch the job status from all the relevant places
and render a static HTML page. We publish that to gitlab Pages,
and setup a scheduled CI pipeline to refresh once an hour or so.

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|