New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add .travis.yaml file #2

Closed
wants to merge 1 commit into
base: master
from

Conversation

Projects
None yet
2 participants
@simbabque

simbabque commented Feb 11, 2018

This adds Travis and Coveralls support. TravisCI is a continuous integration system that is free for open source projects. It allows you to automatically run your tests whenever you push a branch or someone creates a PR. I've set my branch up in my own account for you to take a look at https://travis-ci.org/simbabque/SQLite-Work.

In order to use it, you need to create an account at https://travis-ci.org/ and sync it with your github account.

In addition to that, there is also https://coveralls.io/, which is hooked up to Travis. It collects coverage data from the test runs in Travis. You can look at my fork at https://coveralls.io/github/simbabque/SQLite-Work. Again, you have to create your own account and sync it with your github profile.

This is my entry for the CPAN Pull Request Challenge in February 2018. It was intended to be for January, but I unfortunately did not have time to work on it earlier.

@rubykat

This comment has been minimized.

Owner

rubykat commented Aug 2, 2018

I don't use Travis, so this is not useful to me.

@rubykat rubykat closed this Aug 2, 2018

@simbabque

This comment has been minimized.

simbabque commented Aug 2, 2018

The idea was to make it easier for you to start using it. I find it really handy, but the initial setup can be a bit confusing.

@rubykat

This comment has been minimized.

Owner

rubykat commented Aug 2, 2018

I don't have time for the learning curve required, right now, and I'd rather not have things in my code that I'm not using -- that way lies bit rot. But thanks for the thought. I find the testing in Dist::Zilla to be good enough for me; even if it doesn't automatically test every commit, it does auto-test before a new version release. Yeah, it's perl-centric, but that's what I'm mostly writing in.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment