Using Jenkins for Continuous Integration of Perl components OSD2011
5 likes10,949 views
The document discusses implementing Perl testing within a continuous integration environment using Jenkins. It specifically addresses setting up test configurations, enabling JUnit support, and managing coverage reports. The content highlights the importance of testing and offers links to additional resources for further reading.
Using Jenkins for Continuous Integration of Perl components OSD2011
- 1. PERL AND CONTINUOUS INTEGRATION WITH JENKINS jonasbn@dk-hostmaster.dk
- 3. SUBVERSION
- 4. SUBVERSION
- 5. BUILD SYSTEM
- 6. BUILDING
- 7. TESTING
- 8. TESTING MORE
- 9. TESTING EVEN MORE
- 10. # Courtesy of Jeffrey Ryan Thalhammer # http://search.cpan.org/~thaljef/Test-Perl-Critic/lib/Test/Perl/Critic.pm # The severity parameter interpretation was added by jonasbn # See: http://logiclab.jira.com/wiki/display/OPEN/Test-Perl-Critic # $Id$ # $HeadURL$ use strict; use warnings; use File::Spec; use Test::More; use English qw(-no_match_vars); use Test::Perl::Critic; if ( not $ENV{TEST_CRITIC} ) { my $msg = 'Author test. Set $ENV{TEST_CRITIC} to a true value to run.'; plan( skip_all => $msg ); } my $rcfile = File::Spec->catfile( 't', 'perlcriticrc' ); Test::Perl::Critic->import( -profile => $rcfile, -severity => ($ENV{TEST_CRITIC} and $ENV{TEST_CRITIC} >= 0 and $ENV{TEST_CRITIC} <= 5) ? $ENV {TEST_CRITIC} : 5 ); all_critic_ok();
- 11. ENABLING JUNIT
- 12. ENABLING JUNIT
- 13. TIMINGS?
- 14. PROVE
- 15. TIMINGS!
- 16. COVERAGE TEST
- 17. HTML PUBLISHER PLUGIN
- 18. EXTENDED MENU
- 19. COVERAGE REPORT