On 7/19/17 6:59 PM, Alessandro Pasotti wrote:

> On Wed, Jul 19, 2017 at 5:53 PM, Matthias Kuhn <matth...@opengis.ch
> <mailto:matth...@opengis.ch>> wrote:
>
>     Hi,
>
>     Travis CI stopped working today and reported nothing but failures.
>
>     # The good news
>
>     It's up and running again.
>
>     # Affected pull requests
>
>     If you have a pull request which errored, either push a new commit to
>     your branch (if you have something that you wanted to push anyway) or
>     close and reopen the pull request.
>
>     # Cause
>
>     It was caused by the switch of the default distribution from
>     precise to
>     trusty. (Read more about it here
>     https://blog.travis-ci.com/2017-07-11-trusty-as-default-linux-is-coming
>     
> <https://blog.travis-ci.com/2017-07-11-trusty-as-default-linux-is-coming>).
>     Right now it's quite easy to revert (once you know what's actually
>     going
>     on).
>
>     # Perspective
>
>     Mid-term we will have to migrate to something newer though.
>     Travis also offers support for trusty but that's quite old as well. We
>     are currently looking into a couple of different approaches like
>     building our depencies for trusty and shipping them via a ppa or
>     using a
>     docker container with the dependencies. The main requirement is
>     that the
>     whole dependency build process is scripted and can be done
>     collaboratively (something the current osgeo4travis dependencies don't
>     fulfill which I'm eager to retire).
>
>     Cheers
>     Matthias
>
>
>
> Thanks Matthias for the good news, you know we (@ boundless) have an
> established workflow for nightly builds of docker QGIS testing images,
> basically the docker images are build with Vagrant on AWS through a
> jenkins task that schedules the builds and pushes them to docker hub.
>
> The images are then pulled by Travis and the tests are run inside the
> docker images on Travis.
>
> Maybe something similar can be developed for the dependencies, please
> le me know if we can help.

That's very interesting, Alessandro

How are dependencies built, using some packaging system or a set of
scripts? Are the scripts or recipes around somewhere?

We were wondering if this could be done directly on travis before the
build starts (skipping any package that is already up to date in the cache).
The nice benefit of this compared to a separate build as you are doing
on AWS would be that if something needs a new dependency (thinking of
qca, qtkeychain, ...) it can directly integrated in the same pull request.
What do you think about this approach?

Thanks
Matthias

>
>
> Cheers.
>
> -- 
> Alessandro Pasotti
> w3:   www.itopen.it <http://www.itopen.it>

_______________________________________________
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Reply via email to