keathley / wallaby / 843 / 7
85%
master: 85%

DEFAULT BRANCH: master
Ran
Files 23
Run time 1s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 61.216% (-4.2%) from 65.405%
WALLABY_DRIVER=phantom

push

travis-ci

web-flow 
Reduce number of travis builds (#288)

* Reduce number of travis builds

Right now we generate [40](https://travis-ci.org/keathley/wallaby/builds/257458811) travis builds. That is a bit too much, I don't want my Travis friends to come over and be like "Tobi, you are using up all our resources!"
On a more serious note, we should fairly use our given free resources. Also, we sometimes have weird troubles downloading drivers etc. (which we should try to fix) but the more builds we have the more likely this is to occur and then we gotta restart etc... also, of course - it takes quite long.

So, of all the things we test what can we let go off?

* We need to test all drivers
* we need to test all elixir versions
* We need to test all combinations of drivers and elixir versions as they might execute different code from our driver integration and I wanna avoid issues where we start calling methods that don't exist yet in 1.3 for instance 

So, what can we do? Well my suggestion is this: Run each elixir version with its "dedicated" OTP release:
* 1.3 on 18,
* 1.4 on 19
* 1.5 on 20

that way we test all dirvers on all elixir versions, we test all otp releases, the only thing that might bite us is a bug that just occurs with elixir 1.5 and erlang 18 for instance which I think is the least likely to occur.

What do you think?

I hope my changes create the build matrix I imagine :D

* Instead of include, try the exclude road!

* Syntax error like the bash pro that I am (not)

453 of 740 relevant lines covered (61.22%)

17368.72 hits per line

Source Files on job 843.7 (WALLABY_DRIVER=phantom)