[PATCH-for-5.1] .travis.yml: Deprecate it in favor of GitLab CI

[Daniel P. Berrangé]

On Tue, Aug 04, 2020 at 10:30:40AM +0200, Philippe Mathieu-Daudé wrote:
> As of QEMU 5.2 we prefer to focus our CI development on GitLab.
> Mark Travis-CI as deprecated (adding a big warning).
> 
> Signed-off-by: Philippe Mathieu-Daudé <philmd at redhat.com>
> ---
>  docs/system/deprecated.rst | 11 +++++++++++
>  .travis.yml                |  7 +++++++
>  2 files changed, 18 insertions(+)
> 
> diff --git a/docs/system/deprecated.rst b/docs/system/deprecated.rst
> index 851dbdeb8a..c17a5b0896 100644
> --- a/docs/system/deprecated.rst
> +++ b/docs/system/deprecated.rst
> @@ -17,6 +17,17 @@ they were first deprecated in the 2.10.0 release.
>  What follows is a list of all features currently marked as
>  deprecated.
>  
> +Build and test automation
> +-------------------------
> +
> +``Travis-CI`` (Since 5.2)
> +'''''''''''''''''''''''''
> +
> +``Travis-CI`` is deprecated in favor of GitLab-CI.
> +
> +The '.travis.yml' configuration should only be modified to remove jobs
> +when equivalent exist on GitLab-CI. Adding new jobs is not allowed.

I don't think this is really needed. CI is not an end user feature
that is covered by deprecation policy. We simply do whatever we want
with CI at any time that suits maintainers.

>  System emulator command line arguments
>  --------------------------------------
>  
> diff --git a/.travis.yml b/.travis.yml
> index 6695c0620f..4ad243f511 100644
> --- a/.travis.yml
> +++ b/.travis.yml
> @@ -1,3 +1,10 @@
> +#  WARNING  WARNING  WARNING  WARNING  WARNING  WARNING  WARNING  WARNING
> +#
> +#  As of QEMU 5.2, this file is now deprecated in favor of GitLab CI.
> +#  Do not modify, except to remove jobs ported to GitLab CI.
> +#
> +#  WARNING  WARNING  WARNING  WARNING  WARNING  WARNING  WARNING  WARNING

  NOTE: GitLab provides the primary CI platform, with Cirrus CI
        as the preferred secondary. No new jobs or functionality
	should be added to Travis. The intent is to eliminate
	Travis whereever possible.

More broadly we would benefit from having a ci.rst file somewhere
in docs/ to explain our setup and strategy

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 :|