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://localrepo/jenkins";,
descr => "Jenkins local repo",
enabled => "1",
gpgcheck => "1",
mirrorlist => absent,
gpgkey => "http://localrepo/jenkins/jenkins-ci.org.key";, }
}
Why not simply do something like:
class internalJenkins {
require yum::repo::jenkins
}
And manage all repos in another module?
Thats how we also do it. All repos are configured in one rep0 module.
We do have both plain mirrored en own build repo modules. Supporting
multiple distro and version.
Maintenance of the packages and updates are done outside of puppet of
course. Configuration af course with.
We use a proxy in the dms zone, to gain acces to the repo server, which
at this moment is hosted internally.
Grts
--
Johan De Wit
Open Source Consultant
Red Hat Certified Engineer (805008667232363)
Puppet Certified Professional 2013 (PCP0000006)
_________________________________________________________
Open-Future Phone +32 (0)2/255 70 70
Zavelstraat 72 Fax +32 (0)2/255 70 71
3071 KORTENBERG Mobile +32 (0)474/42 40 73
BELGIUM http://www.open-future.be
_______________________________________________________
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
