build perl applications under Jenkins CI server
following packages should be installed:
Build perl project
source directory
directory - if lookup last tag
is set find ‘tagged’ directory with maximum version number and cwd to it - setup local::lib to workspace/cpanlib directory - runs “cpanmini -i .” to install everithing into workspace/cpanlib directorysource directory
directory - copy workspace/cpanlib into current working directory - runs “perl Build.PL && ./Build manifest && ./Build dist” to create cpan distributive - copies cpan distributive to workspace/distributive
directory - doing some cleanuprun build process
: enable/disable build stepsource directrory
: directory where build runs ( should have cpan compatible structure - have Makefile.PL or Build.PL file )lookup last tag
: whether to look up tag with maximum version in source directory
create distributive
: where to create cpan distributive ( will be stored in distributive
directory)verbosity type
: level of verbosityenable catalyst debug mode
: run catalyst tests in debug modePatches are just stanzas in cpanminus client format, they are passed to cpanminus client as arguments. The reason you may want to use patches is to forcefully install some problematic cpan modules or install downgraded versions. Patches are the right way to do this. Once patches are applied you may comment them or prepend with --skip-satisfied
flag. Check out http://search.cpan.org/perldoc?cpanm for details.
Patches examples:
# any comments start with '#'
-f Math::Currency # forcefully installation
--skip-satisfied CGI DBI~1.2
http://search.cpan.org/CPAN/authors/id/D/DO/DOY/Moose-2.0604.tar.gz
You can set environment variables via “Jenkins/Configuration/Global properties/Environment variables” interface to adjust plugin behaviour.
Setup one if you have custom cpan mirror, for example private mini cpan server.
http://my.private.cpan.local
Standard way to do things when you behind http proxy server.
http://my.proxy.server
Setup your standard encoding.
ru_RU.UTF-8