test library on all supported versions (1.3.4 ... 1.7.3)

[revati]

It seems that SemaPhoreCI doesn't provide such functionality, or I didn't find it.

TravisCI on the other had does.

In either case, not selected CI is important, but in fact, that library tests are run in all those environments to ensure most compatibility. Currently is set to elixir 1.7.4.

Previously manually fixed issues, that occurred in CI (because it was set to 1.3.4) but locally used 1.7...

• test in all minor elixir versions starting from 1.3
• test code format on the latest elixir version
• test coverage on the latest elixir version
• reports have ambiguous names of each job, not so self evident from failed job name, which part failed

[hauleth]

You can use Circle CI. While there is no "test matrix" like in Travis CI it is much more flexible solution than Travis (especially as Travis has some bad mojo recently with firing most of their top engineers).

[revati]

Oh, i am somewhat new to CI environments, so will have to look into that. Thanks for the tips

[revati]

I haven't yet have read the documentation, but it is safe to assume to configure CircleCI I will have to provide a hook, to do so, I would need admin privileges for this repo (@nicholasjhenry).

[nicholasjhenry]

@revati you know have admin privileges.

[revati]

@nicholasjhenry Thanks, seems configured CircleCI to run elixir on all minor versions starting from 1.3.4. If you want you can sign up in circle ci with your github user and you will be able to configure and see cabbage project. I don't have access to gherkin project so will leave that one alone

[nicholasjhenry]

Awesome, @revati! Nice to have this on CircleCI. You now have admin access to gherkin. Cheers!

[revati]

Thanks, @nicholasjhenry, will look into it as well. Hopefully this weekend, but most likely only next one.