[Qgis-developer] Testing plugins against QGIS3 with Travis

[Alessandro Pasotti]

On Tue, Sep 27, 2016 at 12:46 PM, Sandro Santilli <strk at kbt.io> wrote:

> On Tue, Sep 27, 2016 at 12:23:39PM +0200, Matthias Kuhn wrote:
> > On 09/27/2016 11:49 AM, Sandro Santilli wrote:
> > > On Tue, Sep 27, 2016 at 11:25:00AM +0200, Alessandro Pasotti wrote:
> > >
> > >> QGIS is already built into the docker images and you don't need to
> buld it
> > >> in a travis job (it would take too long) but yes, the docker pull
> operation
> > >> could take a while.
> > >
> > > Do Travis agent not cache downloaded docker images ?
> >
> > The strategy which we use for QGIS tests (and plugin tests) and some
> > other plugins which I've been involved with do not depend on Docker but
> > instead on a precise or trusty system where additional dependencies can
> > be installed from repositories (which are currently missing for almost?
> > all distributions).
>
> Yes, but Alessandro was suggesting a user to use a docker-based travis
> to test plugins, if I'm not mistaken.
>


Yes, exactly, the Docker image contains QGIS nightlies from different
branches and a few small scripts that make easier to run fully automated CI
tests (unittest python classes)  inside a real QGIS instance.

We are using this system to test plugins and to run integration tests with
GeoServer or other endpoints (they are also in docker containers,
orchestrated with docker compose.



-- 
Alessandro Pasotti
w3:   www.itopen.it
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-developer/attachments/20160927/5578717b/attachment-0001.html>