[7.0]update travis config to properly test odoo modules

[petrus-v]

Try to fix #467 for the moment just copy/paste .travis.yml file from 8.0 branch

[petrus-v]

Hum... do we test PR with travis on this repo?... I'm going to commit a fake commit to trigger travis build on from my repo as I don't know how to launch for the first time travis build without pushing something...

[petrus-v]

What a strange story... this time travis is running the PR!

It failed, not as expected but that's already better than it was! we are now testing odoo modules!

Lets have a look what's wrong with DAV!...

[hbrunn]

looking good so far! For 8.0, this was a quite frustrating exercise because there were a lot of cycles of fixing some small thing, rerunning travis, fix the next etc. You might want to first exclude all modules that cause problems, and only after that reenable them one by one. We're better off with partial tests than with no tests at all.

[petrus-v]

Last commit I've add the installation of pywebdav in travis script but I wonder if it's the good place according OCA practices?!

This time travis is failing as expected! we have to fix it but to me it should be done in an other PR!

[hbrunn]

I think what you do with pywebdav is perfectly fine. It would be preferred to install it in the apt section, but according to https://github.com/travis-ci/apt-package-whitelist/blob/master/ubuntu-precise, it's not available. And requesting it won't do much good I guess because we need a specific version.

👍

[petrus-v]

@hbrunn

thanks for your answers!

[pedrobaeza]

Thanks for bringing this to the old good 7.0!

👍

[StefanRijnhart]

Thanks! 👍

[hbrunn]

I used the new squash-and-merge-feature (https://github.com/blog/2141-squash-your-commits, don't mind the date), yay!

[StefanRijnhart]

Oh dear, that new feature is going to wreak havoc on those of us who let their old PRs linger in the merge section of their buildouts after they have been squashed-and-merged...

[pedrobaeza]

Which date is used then?