Looking at the code we found out that parts of it made no sense. Asbjørn provided me with a good example demonstrating the bug, so this was quickly translated to a test (BDKPHN-10) and the non-sense code and the issue could be addressed.

The release has been uploaded to PAUSE and should be available on CPAN.

Thanks to Asbjørn for reporting the bug.

jonasbn, Copenhagen

PS. this post was cross-posted from the project blog on Business::DK::Phonenumber

Task::Jenkins is a collection of distributions for continuous integration using Jenkins it installs a collection of distributions which have been identified as useful in utilizing Jenkins for continuous integration of Perl distributions, applications and code.

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, 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 standard tool chain components like Test::Harness works out of the box.

For a tutorial on how to get started please see the wiki page on Continuous Integration with Perl.

The distribution is a Task based distribution, so it does not contain any code as such, but simply bundles existing distributions for easy handling. Currently Task::Jenkins contain:

- App::Prove

- Devel::Cover

- TAP::Formatter::JUnit

Suggestions, feedback, patches etc. most welcome,

jonasbn

PS. this post was cross-posted from the project blog on Task::Jenkins

The issue was labelled: BDKFI-20. The change can be inspected in Fisheye.

The distribution will be made available via CPAN and your local mirror shortly or you can go to MetaCPAN.

Thanks to my colleague Erik Johansen for the assistance and pointer to what the problem was.

jonasbn, Copenhagen

This post was cross-posted from: logicLAB.jira.com

The two releases introduces two new policies of mine:

• Perl::Critic::Policy::logicLAB::RequireSheBang
• Perl::Critic::Policy::logicLAB::ProhibitShellDispatch

The two policies focus on addressing interaction in, which your Perl components are working. Extending on the path that was set out with the release of Perl::Critic::Policy::logicLAB::ProhibitUseLib

Both new policies are simple policies, but hopefully useful. They are already giving me good feedback and value being put to use on a Continues Integration platform Jenkins.

All should be available on CPAN by now, both as individual distributions, but also as part of the Perl::Critic::logicLAB bundle mentioned here.

Feedback and patches most welcome,

jonasbn, Copenhagen

More information, registration and talks at:

http://conferences.yapceurope.org/npw2011

I will be there and give some talks, please see the schedule.

http://conferences.yapceurope.org/npw2011/talks

I will personally not be attending because I am out of town at that time, but I really hope you will consider attending the Nordic Perl Workshop 2011 it is usually educational, enlightening and a lot fun…

jonasbn

This year the event will be held at the venue where the Copenhagen Perl Mongers held YAPC::Europe 2008.

As for last year we are hoping to attract some Perl people and Perl talks. Last year we arranged a two-day Perl 6 Hackathon in conjunction with the OSD conference, but this year we aim a little wider.

So please read the Call for Speakers below and forward it to friends, colleagues and fellow Perl mongers.

jonasbn

Call for Speakers
=================

Open Source Days 2011 – Community Edition – will be held on Saturday March 5th
2011, at Copenhagen Business School (CBS), Frederiksberg and we are looking for
gifted, entertaining and technically enlightened speakers for the conference.

Normal Talks – 45 minutes
————————-

Open Source Software has been around the block for quite a while. Every day we
all work with rock-solid software that just works. This year we are interested
in the status of those “goldies” we all take for granted – as well as the new
upcoming savvy projects.

You might be a developer, a community leader, a businessman or a user group
participant seeing the bigger picture or just know your software inside-out -
share your knowledge with us, by giving a talk. Speakers can attend the
conference for free and to some extent we might be able to reimburse your
travel and hotel.

Lightning Talks – 15 minutes
—————————-

Speak your mind – tell us about your idea for a new open source project, how
you made your first android app or something completely different – the only
limit is the time frame – 15 minutes!

If you haven’t tried giving a talk before – this is a good place to start.
Lightning speakers attend the conference for free, but we do not reimburse your
travel expenses.

Tutorials, Workshops and Demos
——————————

If you are just dying to give us a demo of how you hacked your newest gadget,
you want to host an Arduino workshop or you know postfix forwards and backwards
and want to give a tutorial – let us know. Workshops, demos and tutorials have
a time frame set in accordance with the speaker.

Tutorial and workshop speakers will be reimbursed as normal speakers.

Community Booths – Join the Fun
——————————-

Our wish is that the community groups will start planning for their activities
and events for their booths immediately. Open Source Days 2011 – The Community
Edition will deliver the infrastructure and by doing so give the user groups
the best possibly platform for strong community content at the conference.

This year we would like the user groups to submit a description of their
planned activities at their booth as well as a short description on themselves.
Having a descriptive program for activities will greatly help us pick the most
interesting user groups for the conference audience.

Please send your request for a community booth to
ug2011 at opensourcedays.org

together with a description of your planned events no later than February 1st
2011.

Sponsorships
————

We are looking for sponsorships.  A sponsorship can be used for a special
purpose like:

 * Provide a conference t-shirt
 * Provide lunch for the participants
 * Provide conference keyhangers
 * Provide a room for talks or User Groups
 * Provide a conference bag
 * Provide a conference beer-event

Or maybe just a way to show you and your company’s appreciation for open source
software.

Sponsorships can be anywhere in the range DKK 1,000 to DKK 25,000.  Please
write to
sponsor2011 at opensourcedays.org
if you want more information on the
sponsorship opportunities at the conference.

If you are interested in an exhibition booth, you can also contact us, on the
above mail-address.

Get in Touch
————

Please send us a title, a couple of lines about your talk and a short bio to

program2011 at opensourcedays.org
no later than February 1st 2011.

You are also most welcome to write to us if you have any questions regarding
the conference. You can also catch us in the IRC channel #opensourcedays @
EFnet.

If you represent a company, we expect you to state so in your mail.

Feel free to follow us on Twitter:
http://twitter.com/opensourcedays
or
Facebook:
http://www.facebook.com/opensourcedays
to get the latest news about
the conference.

Under the motto of:

There’s more than one way for things to go wrong

More information, registration and talks at:

http://conferences.yapceurope.org/npw2010

I will be there and give some talks, please see the schedule.

http://conferences.yapceurope.org/npw2010/talks

Hope to see you in Reykjavik, Iceland.

jonasbn

I have created a Task implementation bundle listing my two own policies for now (I expect to add other policies used later on). This gives you the opportunity to download the policies by themselves if they look like something you would like to use or you can even bundle them yourself with other policies you make use of.

This packaging is an experiment and is not the recommended way and so it might change in the future, so let me know if you have any feedback on the packaging, both if you are using Perl::Critic::logicLAB or the actual policies directly.

The policies which have also just been released and currently listed in Perl::Critic::logicLAB are:

• Perl::Critic::Policy::logicLAB::ProhibitUseLib
• Perl::Critic::Policy::logicLAB::RequireVersionFormat

Both are simple policies, but hopefully useful.

All should be available on CPAN by now.

jonasbn, Copenhagen

After reading the documentation and doing some considering I decided to deprecate Bundle::JONASBN and then redo the same distribution as Task::BeLike::JONASBN.

The project is in the same repository and Bundle::JONASBN was refactored to support this and the project site was renamed also. Many of the pointers are still using the internally used project key BJONASBN.

The Task concept is fairly easy and being a supporter of KISS, I am thinking about using this concept for other things currently on the drawing board.

Kudos should go to Adam Kennedy for the Task contribution to CPAN, it is simply beautiful in all it’s simplicity.

Task::BeLike::JONASBN has been released to CPAN as version 1.00 making it a major release on the same code base.

Task::BeLike::JONASBN and Bundle::JONASBN will live in parallel for an amount of time, but Bundle::JONASBN will be removed from CPAN eventually and all future development will be centered around Task::BeLike::JONASBN.