From: "Alex Bennée" <alex.bennee@linaro.org>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>
Cc: Fam Zheng <fam@euphon.net>,
Michael Roth <mdroth@linux.vnet.ibm.com>,
Michael Tokarev <mjt@tls.msk.ru>,
qemu-devel@nongnu.org, Bruce Rogers <brogers@suse.com>
Subject: Re: [PATCH v2] .travis.yml: Test the release tarball
Date: Fri, 18 Oct 2019 16:56:38 +0100 [thread overview]
Message-ID: <87v9smnj2h.fsf@linaro.org> (raw)
In-Reply-To: <4fbafa72-321c-2062-f97e-502616ec6c32@redhat.com>
Philippe Mathieu-Daudé <philmd@redhat.com> writes:
> ping?
I've pulled it into testing/next to play but I was wondering if it was
worth it given how infrequently it would run...
>
> On 10/7/19 6:04 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>
>> ---
>> v2: addressed mdroth comments
>> This job is quick enough: Ran for 16 min 33 sec
>> https://travis-ci.org/philmd/qemu/jobs/594565293
>> Based-on: <20191007133540.30623-1-philmd@redhat.com>
>> pull request including "Fix tarball builds of UEFI/EDK2 firmware"
>> https://lists.gnu.org/archive/html/qemu-devel/2019-09/msg02734.html
>> ---
>> .travis.yml | 23 +++++++++++++++++++++++
>> 1 file changed, 23 insertions(+)
>> diff --git a/.travis.yml b/.travis.yml
>> index d0b9e099b9..d881ea0849 100644
>> --- a/.travis.yml
>> +++ b/.travis.yml
>> @@ -339,3 +339,26 @@ 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'.
>> + # This is the case when release candidate tags are created.
>> + - if: tag IS present AND tag =~ /^v\d+\.\d+(\.\d+)?(-\S*)?$/
>> + 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:
>> + - make -C ${SRC_DIR} qemu-${QEMU_VERSION}.tar.bz2
>> + - ls -l ${SRC_DIR}/qemu-${QEMU_VERSION}.tar.bz2
>> + - tar -xf ${SRC_DIR}/qemu-${QEMU_VERSION}.tar.bz2 && cd qemu-${QEMU_VERSION}
>> + - ./configure ${BASE_CONFIG} ${CONFIG} || { cat config.log && exit 1; }
>> + - make install
>>
--
Alex Bennée
next prev parent reply other threads:[~2019-10-18 15:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-07 16:04 [PATCH v2] .travis.yml: Test the release tarball Philippe Mathieu-Daudé
2019-10-18 14:40 ` Philippe Mathieu-Daudé
2019-10-18 15:56 ` Alex Bennée [this message]
2019-10-18 17:08 ` Philippe Mathieu-Daudé
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=87v9smnj2h.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=brogers@suse.com \
--cc=fam@euphon.net \
--cc=mdroth@linux.vnet.ibm.com \
--cc=mjt@tls.msk.ru \
--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).