On 19/05/2015 04:34, Marvin Humphrey wrote:
Configuring for multiple languages is a pain with Travis, unfortunately.

We might get by using multiple environment variables and a custom test script
which recognizes them.

     language: c
     env:
       - CLOWNFISH_HOST=perl
       - CLOWNFISH_HOST=c
       - CLOWNFISH_HOST=go
       - CLOWNFISH_HOST=python
       - CLOWNFISH_HOST=ruby
     script: ./devel/bin/travis-build.sh

That works against testing multiple versions for supported hosts, though.

That was my first idea as well. Testing against multiple Perl versions shouldn't be a problem with a setup like this:

    env:
      - CLOWNFISH_HOST=perl PERL_VERSION=5.8
      - CLOWNFISH_HOST=perl PERL_VERSION=5.10
      ...
      - CLOWNFISH_HOST=perl PERL_VERSION=5.20
      - CLOWNFISH_HOST=c
      - CLOWNFISH_HOST=go
      - CLOWNFISH_HOST=python
      - CLOWNFISH_HOST=ruby

It seems that Travis uses perlbrew internally to set the Perl version:

    https://travis-ci.org/nwellnhof/lucy-clownfish/jobs/63065921#L84

So our travis-build.sh script could simply run `perlbrew use $PERL_VERSION` before running the Perl tests.

Nick

Reply via email to