From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Fam Zheng" <fam@euphon.net>, "Laszlo Ersek" <lersek@redhat.com>,
"Michael Tokarev" <mjt@tls.msk.ru>,
"Michael Roth" <mdroth@linux.vnet.ibm.com>,
"Bruce Rogers" <brogers@suse.com>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [PATCH] .travis.yml: Test the release tarball
Date: Fri, 20 Sep 2019 19:46:16 +0200 [thread overview]
Message-ID: <2348be05-0e20-2a18-483e-7c280b2af5e4@redhat.com> (raw)
In-Reply-To: <20190920174219.22005-1-philmd@redhat.com>
On 9/20/19 7:42 PM, Philippe Mathieu-Daudé wrote:
> Add a job to generate the release tarball and build/install few
> QEMU targets from it.
>
> Ideally we should build the 'efi' target from the 'roms' directory,
> but it is too time consuming.
>
> This job is only triggered when a tag starting with 'v' is pushed,
> which is the case with release candidate tags.
>
> Signed-off-by: Philippe Mathieu-Daudé <philmd@redhat.com>
> ---
> This job is quick enough: Ran for 15 min 32 sec
> https://travis-ci.org/philmd/qemu/jobs/587583631
>
> Based-on: <20190912231202.12327-1-mdroth@linux.vnet.ibm.com>
> "Fix tarball builds of UEFI/EDK2 firmware"
> https://lists.gnu.org/archive/html/qemu-devel/2019-09/msg02734.html
> ---
> .travis.yml | 22 ++++++++++++++++++++++
> 1 file changed, 22 insertions(+)
>
> diff --git a/.travis.yml b/.travis.yml
> index d0b9e099b9..a21f99d22d 100644
> --- a/.travis.yml
> +++ b/.travis.yml
> @@ -339,3 +339,25 @@ matrix:
> - CONFIG="--target-list=xtensa-softmmu,arm-softmmu,aarch64-softmmu,alpha-softmmu"
> - TEST_CMD="make -j3 check-tcg V=1"
> - CACHE_NAME="${TRAVIS_BRANCH}-linux-gcc-default"
> +
> +
> + # Release builds
> + # The make-release script expect a QEMU version, so our tag must start with a 'v'
*sigh* I forgot to commit my stash.
This is simply a change in the comment:
-- >8 --
@@ -342,7 +342,8 @@
# Release builds
- # The make-release script expect a QEMU version, so our tag must
start with a 'v'
+ # The make-release script expect a QEMU version, so our tag must
start with a 'v'.
+ # This is the case when release candidate tags are created.
---
> + - if: tag IS present AND tag =~ ^v
> + env:
> + # We want to build from the release tarball
> + - BUILD_DIR="release/build/dir" SRC_DIR="../../.."
> + - BASE_CONFIG="--prefix=$PWD/dist"
> + - CONFIG="--target-list=x86_64-softmmu,aarch64-softmmu,armeb-linux-user,ppc-linux-user"
> + - TEST_CMD="make install -j3"
> + - QEMU_VERSION="${TRAVIS_TAG:1}"
> + - CACHE_NAME="${TRAVIS_BRANCH}-linux-gcc-default"
> + before_script:
> + - command -v ccache && ccache --zero-stats
> + - mkdir -p ${BUILD_DIR} && cd ${BUILD_DIR}
> + script:
> + - ${SRC_DIR}/scripts/make-release ${SRC_DIR} ${QEMU_VERSION}
> + - ls -l qemu-${QEMU_VERSION}.tar.bz2
> + - tar -xf qemu-${QEMU_VERSION}.tar.bz2 && cd qemu-${QEMU_VERSION}
> + - ./configure ${BASE_CONFIG} ${CONFIG} || { cat config.log && exit 1; }
> + - make install
>
next prev parent reply other threads:[~2019-09-20 17:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-20 17:42 [PATCH] .travis.yml: Test the release tarball Philippe Mathieu-Daudé
2019-09-20 17:46 ` Philippe Mathieu-Daudé [this message]
2019-09-23 13:44 ` Michael Roth
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=2348be05-0e20-2a18-483e-7c280b2af5e4@redhat.com \
--to=philmd@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=brogers@suse.com \
--cc=fam@euphon.net \
--cc=lersek@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=mjt@tls.msk.ru \
--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).