comment on

Thats pretty much what im working on right at this moment.

Im creating a package that will pull code from CVS, package it up into a RPM and then it will be released via yum.

All will be configure via a YAML file, so the general thought is that the developer will tag the CVS module, and the release manager will update the YAML file with the tag (he has little unix experience so i am following KISS). And a script would check out the source, turn it into a RPM and then via yum update the target system.

The nice thing about it is that via RPM it is possible to figure out if there have been any changes on the production system.

Unfortunately I have found the RPM modules on CPAN to be a little lacking so im doing a rewrite of one of them to have a little more cleaner interface and fix the bugs. Add to that i only started a couple of days ago so i don't really have much to show for it yet apart from these comments.

In reply to Re^2: Distributing code to 100's of servers by absolut.todd
in thread Distributing code to 100's of servers by perlofwisdom

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.


Think about Loose Coupling
	PerlMonks