[libvirt] [PATCH python] Add travis build config

[Daniel P. Berrange]

On Tue, Sep 19, 2017 at 03:06:58PM +0200, Martin Kletzander wrote:
> On Tue, Sep 19, 2017 at 12:56:55PM +0100, Daniel P. Berrange wrote:
> > Enable builds on several python versions, and against several versions
> > of libvirt. Ideally we would build all the way back to 0.9.11, since
> > that is the min supported libvirt for python binding. It is not possible
> > to build this old libvirt version on modern distros though, so using
> > 1.2.0 as the oldest for now.
> > 
> > Signed-off-by: Daniel P. Berrange <berrange at redhat.com>
> > ---
> > .travis.yml | 55 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > setup.py    | 13 +++++++------
> > 2 files changed, 62 insertions(+), 6 deletions(-)
> > create mode 100644 .travis.yml
> > 
> > diff --git a/.travis.yml b/.travis.yml
> > new file mode 100644
> > index 0000000..203d91d
> > --- /dev/null
> > +++ b/.travis.yml
> > @@ -0,0 +1,55 @@
> > +language: python
> > +os: linux
> > +
> > +python:
> > +  - 2.6
> > +  - 2.7
> > +  - 3.2
> > +  - 3.6
> > +
> > +env:
> > +  - LIBVIRT=1.2.0 EXT=gz
> > +  - LIBVIRT=2.0.0  EXT=xz
> > +  - LIBVIRT=3.6.0  EXT=xz
> 
> Spacing should be same on all lines.
> 
> > +
> > +install:
> > +  - sudo apt-get -qqy build-dep libvirt libxml2-dev
> > +  - sudo apt-get -qqy install curl
> > +  - pip install lxml nose
> 
> It'd be nice to have pip install -r requirements.txt here (and that file
> added, of course).
> 
> > +  - curl -O -s https://libvirt.org/sources/libvirt-${LIBVIRT}.tar.${EXT}
> > +  - tar -xf libvirt-${LIBVIRT}.tar.${EXT}
> > +  - pushd libvirt-${LIBVIRT}
> > +  - |
> > +        ./configure --prefix=`pwd`/../libvirt-vroot \
> > +                    --without-libvirtd \
> > +                    --without-esx \
> > +                    --without-vbox \
> > +                    --without-libxl \
> > +                    --without-xen \
> > +                    --without-qemu \
> 
> Will this prevent building the qemu-specific APIs?  I'm too lazy to
> check it out and I think there is no harm in seeing that after this is
> pushed, though =)

No, we don't ever disable the public APIs

> Both this and the one above should be regenerated, of course.  Unless
> they were, I don't know how to check those.

The encrypted data was correct - only the comments were wrong


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