Il giorno mar 5 nov 2019 alle ore 10:06 Luca Toscano <toscano.l...@gmail.com> ha scritto: > > Il giorno lun 4 nov 2019 alle ore 19:33 Luca Toscano > <toscano.l...@gmail.com> ha scritto: > > > > 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. > > This is my idea: > > https://github.com/elukey/httpd/blob/trunk/.travis.yml > > https://travis-ci.org/elukey/httpd/builds/607536348 > > Basically what Joe did, but following what the Apache Arrow Project > did. There is a little bit of repetition, but in theory with this > config people are free to add tests for other OSes (osx, windows) and > I will probably be able to add custom ones with Docker to see the > difference in execution timings etc.. (Apache Arrow's test do use > docker, I didn't see it a first). >
I just noticed https://docs.travis-ci.com/user/installing-dependencies/#installing-dependencies-on-multiple-operating-systems, so the 'addons' will be used by travis only if the os can use them (I was afraid of having windows and apt combined). The only thing that I would add to travis.yml are the ifs to separate before_install/script/etc.. for every os, I think that we should add windows as soon as possible.. Do we have a list of build commands to test in Travis? Luca
