Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/jonasbn/tjenkins

Task::Jenkins - collection of distributions for continuous integration using Jenkins
https://github.com/jonasbn/tjenkins

hacktoberfest jenkins perl perl5

Last synced: 10 days ago
JSON representation

Task::Jenkins - collection of distributions for continuous integration using Jenkins

Host: GitHub
URL: https://github.com/jonasbn/tjenkins
Owner: jonasbn
License: artistic-2.0
Created: 2013-12-05T14:06:11.000Z (about 11 years ago)
Default Branch: master
Last Pushed: 2023-12-22T19:33:19.000Z (about 1 year ago)
Last Synced: 2024-12-23T23:24:34.169Z (18 days ago)
Topics: hacktoberfest, jenkins, perl, perl5
Language: Perl
Homepage:
Size: 32.2 KB
Stars: 0
Watchers: 3
Forks: 0
Open Issues: 4
Metadata Files:
- Readme: README
- Changelog: Changes
- License: LICENSE

Awesome Lists containing this project

README

NAME
Task::Jenkins - collection of distributions for continuous integration
using Jenkins

VERSION
This documentation describes version 0.05

SYNOPSIS
% perl Build.PL

% ./Build

% ./Build install

DESCRIPTION
Installation of Jenkins is beyond the scope of this distribution.
Task::Jenkins installs a collection of modules I have identified as
useful in utilizing Jenkins for *continuous integration* of Perl
distributions, applications and code.

The recommended distributions are described in detail below.

The key concept in the use of Jenkins for Perl is enabling the existing
tool chain with minor adjustments.

The basic requirements are that you are using some sort of build system,
I use Module::Build, but other systems should work equally well,
basically you just need some way to initiate an execution of you test
suite from a command line.

The test suite is then expected to output to the console so the output
from the test run can be inspected and the return value of the test run
can be used to indicate whether the test run was a success or failure.

Using basic tool chain components like Test::Harness works out of the
box.

For a tutorial on how to get started please see: .

In order to extend this very basic behaviour you can use some additional
CPAN distributions described below.

TAP::Formatter::JUnit
Jenkins can visualize reports via it's own interface if these reports
are based on JUnit report format. TAP::Formatter can output test reports
in this format using TAP:Formatter::JUnit, so if you are using
Test::Harness you can get beautiful reports using this distribution in
your Jenkins setup.

1 tick the 'Publish JUnit test result report
2 specify the 'Test reports XMLs' as '*-junit.xml' (you have to match
the pattern you specify in you test suite execution string, see above)

Example:

% ./Build test merge=1 tap_harness_args=formatter_class=TAP::Formatter::JUnit > jenkins-${JOB_NAME}-${BUILD_NUMBER}-junit.xml