On Tue, Jul 23, 2013 at 10:01 AM, David E. Wheeler
<[email protected]> wrote:
> I’ve been fiddling with Travis CI, mostly because it’s dead simple to get it
> to build and run tests on many different versions of Perl for every push to
> GitHub.
I'm cool with this.
Note that the ASF already provides continuous integration services:
http://ci.apache.org/buildbot.html
We're already using buildbot. Logan set up our config:
https://svn.apache.org/repos/infra/infrastructure/buildbot/aegis/buildmaster/master1/projects/lucy.conf
Every push to master triggers a build/test run with stock Perl on one of the
FreeBSD machines.
I'm not sure how many different versions of Perl are available to us, but
there's certainly some operating system diversity we aren't taking advantage
of yet.
> I forked Lucy and tried it by adding the attached file to the root
> of the Git repository.
The dev@lucy mailing list strips attachments, but here's the content of that
file:
https://github.com/theory/lucy/blob/1e49a7ccab4bfb62dc045f4a82d02e0f4f0b11e0/.travis.yml
language: perl
perl:
- "5.19"
- "5.18"
- "5.16"
- "5.14"
- "5.12"
- "5.10"
- "5.8"
before_install:
- cd perl
They don't support Perl 5.8 FWIW:
http://about.travis-ci.org/docs/user/languages/perl/#Versions-earlier-than-5.10-Are-Not-Provided
> There were some failures. :-(
We're on it. :)
> Anyway, if you want to run it on Travis, I don’t know if they have some way
> to hook into Apache stuff, but if someone wants has write access to Apache
> repos on GitHub, you can give Travis access then add and push the attached
> file to get it going. Details here:
>
> http://about.travis-ci.org/docs/user/getting-started/
We don't have administrative access to the Apache github mirrors, because
Github doesn't support fine-grained permissions and Infra is understandably
reluctant to give everybody access to everything. However, it looks like a
small number of projects have Travis set up.
https://issues.apache.org/jira/browse/INFRA-6161
https://issues.apache.org/jira/browse/INFRA-4698
https://issues.apache.org/jira/browse/OAK-145
https://issues.apache.org/jira/browse/INFRA-6124
I'd say go ahead and commit .travis.yml to master. After that, I'll get
Travis set up on my github fork just for practice, then take up the matter
with Infra and see what they say.
We may want to be more aggressive about taking advantage of the capabilities
ci.apache.org already offers before pushing too hard, though.
Marvin Humphrey
