[Qgis-developer] Testing plugins against QGIS3 with Travis

[Sandro Santilli]

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.

It could actually also be a good idea to use docker for QGIS, as it
would possibly reduce testing time (a qgis-build-test docker could be
provided with all pre-built dependencies).

We're doing this on Drone for postgis, using ad-hoc docker images, see
https://git.osgeo.org/gogs/postgis/postgis-docker/src/master/build-test

Drone agents cache the image, so all they have to do is fetching the
PostGIS code and build/check that.

--strk;