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

enable Travis CI #1

Closed
wants to merge 2 commits into
base: master
from

Conversation

Projects
None yet
2 participants
@cakirke

cakirke commented Jan 9, 2016

No description provided.

@jkeenan

This comment has been minimized.

Show comment
Hide comment
@jkeenan

jkeenan Jan 9, 2016

Owner

I know that travis has something to do with automated testing but I've never been presented with a rationale for it in relation to a CPAN library like this one. I've never run it, so I don't see what benefit it would be. Can you explain?

(And, no, simply that it's on the list of possible revisions for any module in the PRC is not a sufficient explanation.)

Thank you very much.
Jim Keenan

Owner

jkeenan commented Jan 9, 2016

I know that travis has something to do with automated testing but I've never been presented with a rationale for it in relation to a CPAN library like this one. I've never run it, so I don't see what benefit it would be. Can you explain?

(And, no, simply that it's on the list of possible revisions for any module in the PRC is not a sufficient explanation.)

Thank you very much.
Jim Keenan

@cakirke

This comment has been minimized.

Show comment
Hide comment
@cakirke

cakirke Jan 12, 2016

some benefits of Travis CI

  • automated testing on each push to GitHub
  • simple yaml configuration for most scenarios
  • runs tests against each perl version requested
  • notification of of build status
  • public visibility of build status

you can see an example here:

https://travis-ci.org/cakirke/extutils-modulemaker

and an example of a build status badge here:

Build Status

Chris

cakirke commented Jan 12, 2016

some benefits of Travis CI

  • automated testing on each push to GitHub
  • simple yaml configuration for most scenarios
  • runs tests against each perl version requested
  • notification of of build status
  • public visibility of build status

you can see an example here:

https://travis-ci.org/cakirke/extutils-modulemaker

and an example of a build status badge here:

Build Status

Chris

@jkeenan

This comment has been minimized.

Show comment
Hide comment
@jkeenan

jkeenan Jan 16, 2016

Owner

I'm content with the cross-platform and cross-Perl-version smoke testing I get from cpantesters.org. Unless for some other reason I get into travis in the future, I don't have a strong need for it. So I'm going to pass on this pull request. Thank you very much.

Owner

jkeenan commented Jan 16, 2016

I'm content with the cross-platform and cross-Perl-version smoke testing I get from cpantesters.org. Unless for some other reason I get into travis in the future, I don't have a strong need for it. So I'm going to pass on this pull request. Thank you very much.

@jkeenan jkeenan closed this Jan 16, 2016

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