Tox-powered Travis configuration #133
Conversation
.travis.yml
Outdated
There was a problem hiding this comment.
Won't this install the package outside the tox env?
There was a problem hiding this comment.
Argh, you're right. Suggestions? Create git master tox environments?
There was a problem hiding this comment.
I suppose it would be easier to teach tox about CRYPTOGRAPHY_GIT_MASTER instead.
|
So, apparently there's no easy way to express matrix-style tox envs yet, so we can't do something much nicer than the old travis config. I wrote a script to do the work of creating all the testenv specs by taking the cartesian product of all the possibilities: |
|
Travis appears to be taking a very long time to get around to testing this :( |
coverage does the right thing when you point it at a python file
|
Cool! Now the tests are actually running properly, and we're down to a single failure, which is an unrelated test failure on 0.9.8k. I had accidentally forgot to add the 0.9.8 build back to "allowed-failures". Fixing that now :) |
|
Apparently I hadn't forgotten, but Travis didn't pick it up. I tried being a bit more explicit this time. |
|
Yay! Ready for review now I guess :) |
|
obsoleted by #230 |
4 participants
This makes Travis run a bunch of tox environments. This is good, because it enables moving more behavior into tox. That's good, because it enables running something a lot closer to what CI runs on your own machine.
Refs #127.