qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: "Fam Zheng" <fam@euphon.net>,
	"Peter Maydell" <peter.maydell@linaro.org>,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>,
	qemu-devel@nongnu.org, "Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [PATCH 1/2] travis: Check if docs can be built with multiple Sphinx versions
Date: Mon, 19 Oct 2020 15:42:52 +0100	[thread overview]
Message-ID: <20201019144252.GK236912@redhat.com> (raw)
In-Reply-To: <20201019143109.1034864-1-ehabkost@redhat.com>

On Mon, Oct 19, 2020 at 10:31:08AM -0400, Eduardo Habkost wrote:
> Add new jobs to .travis.yml to test if docs can be built with
> multiple Sphinx versions: 1.6.1, latest 1.x, 2.0.0, and latest
> 2.x.
> 
> Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
> ---
>  .travis.yml | 37 +++++++++++++++++++++++++++++++++++++
>  1 file changed, 37 insertions(+)
> 
> diff --git a/.travis.yml b/.travis.yml
> index 1054ec5d29..f5208301d6 100644
> --- a/.travis.yml
> +++ b/.travis.yml
> @@ -181,6 +181,43 @@ jobs:
>              - perl
>  
>  
> +    # Check we can build docs with multiple Sphinx versions.
> +    # We need --sphinx-build=sphinx-build to ensure we use the
> +    # sphinx-build binary installed by pip.
> +
> +    # 1.6.1 is the oldest Sphinx version we support
> +    - name: "docs (Sphinx 1.6.1)"
> +      env:
> +        - CONFIG="--enable-docs --sphinx-build=sphinx-build"
> +      install:
> +        - pip install -q sphinx==1.6.1
> +      script:
> +        - make -j${JOBS} sphinxdocs
> +    - name: "docs (Sphinx 1.x)"
> +      env:
> +        - CONFIG="--enable-docs --sphinx-build=sphinx-build"
> +      install:
> +        # install latest 1.x version
> +        - pip install -q 'sphinx>=1.0,<2.0'
> +      script:
> +        - make -j${JOBS} sphinxdocs
> +    - name: "docs (Sphinx 2.0.0)"
> +      env:
> +        - CONFIG="--enable-docs --sphinx-build=sphinx-build"
> +      install:
> +        - pip install -q sphinx==2.0.0
> +      script:
> +        - make -j${JOBS} sphinxdocs
> +    - name: "docs (Sphinx 2.x)"
> +      env:
> +        - CONFIG="--enable-docs --sphinx-build=sphinx-build"
> +      install:
> +        # install latest 2.x version
> +        - pip install -q 'sphinx>=2.0,<3.0'
> +      script:
> +        - make -j${JOBS} sphinxdocs

We shouldn't be adding new jobs to Travis CI.

In terms of sphinx versions, we only need to care about versions
that correspond to our supported distro platforms. We have dockerfiles
that we build in GitLab CI for all our important Linux platforms. Some,
but not all,  of the dockerfiles include sphinx already.

IOW, we should add the sphinx RPM to all the dockerfiles that don't
already contain it - centos are the most notable ones missing it.

Then we should make sure there are GitLab CI jobs are trigger the
docs build in all distros that are needed to give this level of
coverage. There shouldn't be a need to install stuff from pip in
this case.

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



      parent reply	other threads:[~2020-10-19 14:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-19 14:31 [PATCH 1/2] travis: Check if docs can be built with multiple Sphinx versions Eduardo Habkost
2020-10-19 14:31 ` [PATCH 2/2] travis: Remove docs from "tools and docs" job Eduardo Habkost
2020-10-19 14:42 ` Daniel P. Berrangé [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20201019144252.GK236912@redhat.com \
    --to=berrange@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=ehabkost@redhat.com \
    --cc=fam@euphon.net \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).