Re^2: Testing CLI commands on Windows machines

Thanks, always wondered what those were. Will look into using them. Continuously uploading to cpan to try to address problems with other platforms is getting old.</>

$PM = "Perl Monk's";
$MCF = "Most Clueless ~~Friar~~ ~~Abbot~~ ~~Bishop~~ ~~Pontiff~~ ~~Deacon~~ ~~Curate~~ Priest";
$nysus = $PM . ' ' . $MCF;
Click here if you love Perl Monks

Comment on Re^2: Testing CLI commands on Windows machines

Replies are listed 'Best First'.
Re^3: Testing CLI commands on Windows machines by pryrt (Abbot) on Sep 12, 2018 at 17:22 UTC
Since no one has mentioned it yet, stevieb has an excellent meditation on setting up Travis-CI for Perl development with multiple versions of perl. I've used his writeup as the starting point for all my CI.	[reply]
Re^3: Testing CLI commands on Windows machines by marto (Cardinal) on Sep 12, 2018 at 15:06 UTC
It's pretty straightforward to setup, and really convenient in terms of getting emailed about failures and so on.	[reply]
Re^4: Testing CLI commands on Windows machines by Anonymous Monk on Sep 12, 2018 at 22:56 UTC
How is it different from cpan testers?	[reply]
Re^5: Testing CLI commands on Windows machines by marto (Cardinal) on Sep 13, 2018 at 08:46 UTC
It's faster, allows for better control over the environment and in order to get something into cpantesters you have to have uploaded it to cpan, at which point automatic mirroring happens and anyone can get it. CI before uploading to cpan allows for the discovery of problems before you release.	[reply]