I'd like to ask a few questions just to clarify the purpose of your plugin.
The idea is that you have a tar.gz ready somewhere that is to be installed on the production server, and that you always install it via a full build cycle. (This isn't at all a bad idea; I've worked at a place that did this for their whole stack - just clarifying).
First question: why not save the tar.gz files as Jenkins build products? This would be easier than managing them yourself.
Second question: why have this plugin do the dependency checking instead of using a Makefile (even a Makefile generated by looking at the Perl dependencies)?
Third question: what's the win over a few lines of shell script to do the same thing?
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.