Re: RFC: Continuous Integration (CI) for your CPAN modules (for free!)

Nice write-up, stevieb, thank you.

I've seen a number of projects using coveralls.io but wasn't really sure what it gives us that Devel::Cover and cpancover don't already. Clearly cpancover only runs on dists published to CPAN, so coveralls.io gives data before publishing which might be useful, I suppose. But the keen author would already use Devel::Cover locally so I'm not really sure of the benefit of using coveralls.io for Perl projects. Could you explain a little about what the advantages are?

Comment on Re: RFC: Continuous Integration (CI) for your CPAN modules (for free!)

Replies are listed 'Best First'.
Re^2: RFC: Continuous Integration (CI) for your CPAN modules (for free!) by stevieb (Canon) on Jan 15, 2016 at 17:22 UTC
Technically, there isn't a whole lot of advantage, except its automatic on each push and easy to view at a glance, and like you said, it's nice for non-CPAN modules (or releases you haven't put up yet). I could see another benefit if there's a small team working on a project, instead of everyone having to use Devel::Cover on each commit/push, they can simply go to a single website to monitor testing progress. I like to browse MetaCPAN every few days and peek into modules that I might like, or for issues in others modules I might want to take a crack at fixing, and I had just found it handy to have a basic coverage percent icon right up front (it shows a (very basic) indicator of effort on testing quality), so I started doing it for my modules. It wouldn't be worth it if it was difficult or time consuming to configure, but it's brain dead simple :)	[reply]

Replies are listed 'Best First'.

Re^2: RFC: Continuous Integration (CI) for your CPAN modules (for free!)
by stevieb (Canon) on Jan 15, 2016 at 17:22 UTC

Technically, there isn't a whole lot of advantage, except its automatic on each push and easy to view at a glance, and like you said, it's nice for non-CPAN modules (or releases you haven't put up yet). I could see another benefit if there's a small team working on a project, instead of everyone having to use Devel::Cover on each commit/push, they can simply go to a single website to monitor testing progress.

I like to browse MetaCPAN every few days and peek into modules that I might like, or for issues in others modules I might want to take a crack at fixing, and I had just found it handy to have a basic coverage percent icon right up front (it shows a (very basic) indicator of effort on testing quality), so I started doing it for my modules.

It wouldn't be worth it if it was difficult or time consuming to configure, but it's brain dead simple :)

[reply]