On Fri, Sep 13, 2013 at 04:20:22PM +0100, alex.ben...@linaro.org wrote:
> From: Alex Bennée <a...@bennee.com>
>
> While QEMU already has various continuous integration set-ups in
> buildbot and commercial Jenkins setups there is some value in supporting
> travis-ci as well. It is well integrated into GitHub work flow and will
> trigger on all branch pushes and pull requests. This makes it easier for
> an individual to kick off smoke tests on a work-in-progress branch
> before eventual submission of patches/pull requests upstream.
>
> The build matrix is currently split by target architecture because a
> full build of QEMU can take some time. This way you get quick feedback
> for any obvious errors.
> ---
> .travis.yml | 19 +++++++++++++++++++
> 1 file changed, 19 insertions(+)
> create mode 100644 .travis.yml
Looks useful. To get more code coverage, flesh out the build
environment:
before_install:
- git submodule update --init --recursive
- sudo apt-get update -qq
- sudo apt-get install -qq \
libgtk-3-dev libvte-2.90-dev libiscsi-dev librados-dev \
libvdeplug-dev libseccomp-dev libsdl1.2-dev \
libgnutls-dev libpng12-dev libncurses5-dev \
libpixman-1-dev libssh2-1-dev libspice-server-dev \
libspice-protocol-dev libnss3-dev libusb-1.0-0-dev \
libusbredirparser-dev
I didn't test this but went through ./configure and looked up the Ubuntu
packages which Travis should have access to.
You can check the config.log output to verify that optional components
were enabled and the libraries were detected.
Stefan
