On 1/25/13 8:33 AM, Joel Berger wrote:
If we are going to start proposing online edits (not
fork/clone/pull-req) we should setup a travis smoker, which will
automatically run smoke tests (but only on ubuntu). This prevents
merging a non-tested non-runnable pull which is easier to happen from an
online-only edit.
Joel
Note that it is *very* easy to set up Travis so that it runs the tests
on each check in to github. See
http://about.travis-ci.org/blog/announcing_python_and_perl_support_on_travis_ci/
and here's an example of a successful run for a randomly-selected
perl-based project
https://travis-ci.org/PerlDancer/Dancer2/jobs/4369785
and for one that failed
https://travis-ci.org/PerlDancer/Dancer2/jobs/3948879
This was done just by creating a .travis.yaml file in the top level -
e.g. see
https://github.com/PerlDancer/Dancer2/blob/master/.travis.yml
and then authorizing travis/github to talk to each other (I think that's
about it; the trick comes in getting the yaml file set up correctly for
PDL).
I strongly recommend it, whatever you decide for the development process.
Doug
_______________________________________________
Perldl mailing list
[email protected]
http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
