comment on

In my continuing quest to make my life easier I've been trying to use Jenkins to stage distributions of software (and Puppet modules) for distribution into the production environment. Since I've been going great guns lately writing Perl based tools that's been including writing my own Perl modules.

I latched onto cpan2rpm as a way to create RPMs to allow Puppet to distribute my modules as needed. Works manually but doesn't seem to work from within a Jenkins job.

Anymonk have any experience with this?

Here is cpan2rpms last few words before the job exits abnormally:

+ cpan2rpm --no-sign .

-- cpan2rpm - Ver: 2.028 --
Upgrade check
Fetch: HTTP

-- module: /var/lib/tomcat6/webapps/jenkins/workspace/Perl JSON --
Metadata retrieval
Build step 'Execute shell' marked build as failure
Finished: FAILURE
[download]

Unfortunately not very informative.

Peter L. Berghold -- Unix Professional
Peter -at- Berghold -dot- Net; Blog: http://blog.berghold.net Warning: No political correctness allowed.

In reply to cpan2rpm and Jenkins (not so perfect together?) by blue_cowdawg

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Just another Perl shrine
	PerlMonks