On 04/17/2013 12:56 PM, Jakov Sosic wrote:
On 12/31/2012 07:40 PM, Matthew Barr wrote:
class internalJenkins
{
include jenkins::repo
include internalJenkins::repo # Inherits jenkins::repo
}
class internalJenkins::repo inherits jenkins::repo {
yumrepo { "jenkins":
baseurl => "http://l
On 12/31/2012 07:40 PM, Matthew Barr wrote:
> class internalJenkins
> {
> include jenkins::repo
>
> include internalJenkins::repo # Inherits jenkins::repo
> }
>
> class internalJenkins::repo inherits jenkins::repo {
> yumrepo { "jenkins":
> baseurl => "http://localrepo/jenkins";,
> descr
:(
I was really asking after the puppet side of dealing w/ a module that wants to
install it's own repo's, vs the below.
Anyone else have any thoughts from the original post?
On Dec 31, 2012, at 1:56 PM, Dan White wrote:
> Here's what I do on the systems I manage:
>
> I use Cobbler and Pupp
ed to contact us.”
Bill Waterson (Calvin & Hobbes)
- Original Message -
From: "Matthew Barr"
To: puppet-users@googlegroups.com
Sent: Monday, December 31, 2012 1:40:26 PM
Subject: [Puppet Users] Modules, yum repo's & best practices
I'm working with a forge modul
I'm working with a forge module that specifies & installs a yum repo before it
installs the packages, then goes about it's business.
* package isn't part of a standard repo
We operate on a policy of minimizing the amount of external repo's we use,
especially on the edge systems.
