[Qgis-developer] Failing tests consider blockers

Larry Shaffer larrys at dakotacarto.com
Sun Feb 16 19:09:59 PST 2014

Hi Jürgen,

On Sun, Feb 16, 2014 at 3:41 PM, Jürgen E. <jef at norbit.de> wrote:

> Hi Larry,
> On Sat, 15. Feb 2014 at 13:11:50 -0700, Larry Shaffer wrote:


All of your comments on unit tests make sense to me.

> > I am suggesting to have official or sponsored CI servers as a
> preventative
> > measure. For example, many github accounts have a CI server hooked into
> their
> > pull requests. This way, the repo maintainers have a constant check as to
> > whether the proposed change builds and passes tests *before* the request
> is
> > merged.
> We could use travis[1] for that (other OSGeo projects already do). But I
> think
> there is no coverage for OSX and Windows there.

Excellent! Thanks for pointing me in that direction.

This time I looked into Travis, I found they now have OS X support [0], and
it supports the Homebrew project for installing dependencies. This is
*very* good, since they do not offer the new caching feature for Mac, only
Linux [1]. I imagine the caching will be very important for any QGIS Travis
setups, since their build process means starting up a VM then reverting it
after completion, i.e. all dependencies would need to be built or installed
from binary packages.

The caching feature just pulls from an offsite Amazon S3 bucket, which is
what I also use for the Mac nighties. This means I can leverage Homebrew to
produce 'bottles' (binary install packages) and store them in my (or an
OSGeo) bucket. Homebrew will then install all needed dependencies, similar
to how Travis's cache works.

This also means I can fully setup Travis and test its integration on my own
QGIS fork first. I can also set up a script to auto-update my fork from
QGIS/master which will give some metrics, including bandwith usage on my S3
bucket (which is cheap).

Though the available CI environment for OS X is only at version 10.8.5 (not
10.9.1), that is better than nothing at all, considering Travis is free and
most QGIS devs aren't testing on Mac.  :-)

> Not sure where to get OSX servers and how much that would cost, but at
> Hetzner
> Windows 2012 R2 Standard Edition costs 25 EUR extra a month (ie. 84 EUR a
> month
> for Windows Server).  But both could probably be integrated with jenkins
> on the
> new servers and also take over the nightly builds.
> But that also only makes real sense once the tests are fixed (for what we
> don't
> need any of the above).

OK, I see your point now. Thanks for explaining it.

[0] http://docs.travis-ci.com/user/osx-ci-environment/
[1] http://docs.travis-ci.com/user/caching/



> Jürgen
> [1] http://docs.travis-ci.com/user/getting-started/
> --
> Jürgen E. Fischer         norBIT GmbH               Tel. +49-4931-918175-31
> Dipl.-Inf. (FH)           Rheinstraße 13            Fax. +49-4931-918175-50
> Software Engineer         D-26506 Norden
> http://www.norbit.de
> --
> norBIT Gesellschaft fuer Unternehmensberatung und Informationssysteme mbH
> Rheinstrasse 13, 26506 Norden
> GF: Jelto Buurman, HR: Amtsgericht Emden, HRB 5502
> _______________________________________________
> Qgis-developer mailing list
> Qgis-developer at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-developer
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-developer/attachments/20140216/50c7dc3e/attachment.html>

More information about the Qgis-developer mailing list