From: Eduardo Habkost <ehabkost@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Fam Zheng" <fam@euphon.net>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: [PATCH 2/2] travis: Remove docs from "tools and docs" job
Date: Mon, 19 Oct 2020 10:31:09 -0400 [thread overview]
Message-ID: <20201019143109.1034864-2-ehabkost@redhat.com> (raw)
In-Reply-To: <20201019143109.1034864-1-ehabkost@redhat.com>
We have other jobs that will test documentation builds, so we
don't need to build docs in that job.
Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
---
.travis.yml | 7 +++----
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/.travis.yml b/.travis.yml
index f5208301d6..626b61b077 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -166,18 +166,17 @@ jobs:
- TEST_CMD="make check-unit -j${JOBS} V=1"
- # Check we can build docs and tools (out of tree)
- - name: "tools and docs (bionic)"
+ # Check we can build tools (out of tree)
+ - name: "tools (bionic)"
dist: bionic
env:
- BUILD_DIR="out-of-tree/build/dir" SRC_DIR="../../.."
- - BASE_CONFIG="--enable-tools --enable-docs"
+ - BASE_CONFIG="--enable-tools --disable-docs"
- CONFIG="--target-list=x86_64-softmmu,aarch64-linux-user"
- CACHE_NAME="${TRAVIS_BRANCH}-linux-gcc-default"
addons:
apt:
packages:
- - python3-sphinx
- perl
--
2.28.0
next prev parent reply other threads:[~2020-10-19 14:37 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 ` Eduardo Habkost [this message]
2020-10-19 14:42 ` Daniel P. Berrangé
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=20201019143109.1034864-2-ehabkost@redhat.com \
--to=ehabkost@redhat.com \
--cc=alex.bennee@linaro.org \
--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).