Hi Joe, Il giorno lun 4 nov 2019 alle ore 17:16 Joe Orton <jor...@redhat.com> ha scritto: > > Here is a proof of concept - > > https://github.com/notroj/httpd/blob/a73adfc8f1c01fbb6a3d493582f9c49c7c942756/.travis.yml > > This runs using the full test suite using a few different configurations > and also does builds with -Werror and maintainer-mode - > > https://travis-ci.org/notroj/httpd/builds/607213820 > > ...this should be very easy to extend with more configurations. > > Can we merge the docker way with this kind of matrix type travis > configuration? >
The proof of concept looks great, I wanted to test something similar especially to get timings. It looks like a single test takes from 2 to 5 minutes maximum, that is really impressive, I thought it would have been more. With Docker in theory we could use the os matrix, but the documentation doesn't really suggest any best practice. My idea was to pull different docker images (previously built and uploaded to Docker Hub), and depending on the os in the matrix run the correct docker command in the "script" section (to get an idea https://github.com/apache/arrow/blob/master/.travis.yml, even if they don't use docker). While I research though it might be good to follow your solution and just have a simple Travis file for say ubuntu and windows. Even if it takes 30 mins to complete, it would be a good feedback for anybody committing code to trunk/2.4.x. And it could be possible that this solution is good enough for our use cases, only testing will tell us! So feel free to commit your Travis config to trunk, maybe following the Apache Arrow example? If so others, more experienced with Windows, might be able to chime in and add the missing configuration. Thanks! Luca
