Hi all, We''re keeping all our modules in Git and we run automated tests against them using Hudson including building virtual servers using cucmber-vhost and deploying our configs via puppet to these vhosts. I''ve now run into two problems: 1) I''m not sure how to get Hudson to merge the "staging" branch into "master" when the tests complete 2) I''m struggling to find a way for puppet 0.25 to perform a "git pull" on all the master branches _before_ it runs to ensure that the latest configs are being distributed. I realise that there may not be many who can help with (1), however I''m fairly sure I''m not alone in using Git for my manifests and I''m wondering how others get their puppetmaster to always run the latest manifest versions from a git repo. Thanks in advance, Matt -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On 10 September 2010 11:16, Matt Wallace <lists@truthisfreedom.org.uk>wrote:> > > 1) I''m not sure how to get Hudson to merge the "staging" branch into > "master" > when the tests complete > >I''ve not used that bit of the Hudson Git plugin, but you can tell it to merge if your build passes: "You''re done. Commits should now be automatically merged with the integration branch (they will fail if they do not merge cleanly), and built. If the build succeeds, the result of the merge will be pushed back to the remote git repository." (http://wiki.hudson-ci.org/display/HUDSON/Git+Plugin)> 2) I''m struggling to find a way for puppet 0.25 to perform a "git pull" on > all > the master branches _before_ it runs to ensure that the latest configs are > being distributed. > >Not sure you can, unless you run each client standalone. How about Hudson invoking something on the puppetmaster when the build passes? J. -- Julian Simpson The Build Doctor Ltd. http://www.build-doctor.com julian@build-doctor.com (+44) 207 183 0323 -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Sep 10, 2010, at 3:16 AM, Matt Wallace wrote:> 2) I''m struggling to find a way for puppet 0.25 to perform a "git pull" on all > the master branches _before_ it runs to ensure that the latest configs are > being distributed.So you want the puppetmaster to run a "git pull" every time it tries to compile a manifest? That would be really expensive in terms of compile time and bandwidth with almost any load.> I realise that there may not be many who can help with (1), however I''m fairly > sure I''m not alone in using Git for my manifests and I''m wondering how others > get their puppetmaster to always run the latest manifest versions from a git > repo. > > Thanks in advance,-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Friday 10 Sep 2010 11:33:31 Patrick wrote:> On Sep 10, 2010, at 3:16 AM, Matt Wallace wrote: > > 2) I''m struggling to find a way for puppet 0.25 to perform a "git pull" > > on all the master branches _before_ it runs to ensure that the latest > > configs are being distributed. > > So you want the puppetmaster to run a "git pull" every time it tries to > compile a manifest? That would be really expensive in terms of compile > time and bandwidth with almost any load.More of a case that something on the puppetmaster watches "master" for each repo and pulls if something changes, but yes, I want puppet to be using the latest version of the manifests every time it runs, although I share the concerns about compile time etc. M. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Friday 10 Sep 2010 11:29:31 Julian Simpson wrote:> On 10 September 2010 11:16, Matt Wallace <lists@truthisfreedom.org.uk>wrote: > > 1) I''m not sure how to get Hudson to merge the "staging" branch into > > "master" > > when the tests complete > > I''ve not used that bit of the Hudson Git plugin, but you can tell it to > merge if your build passes: > > "You''re done. Commits should now be automatically merged with the > integration branch (they will fail if they do not merge cleanly), and > built. If the build succeeds, the result of the merge will be pushed back > to the remote git repository." > > (http://wiki.hudson-ci.org/display/HUDSON/Git+Plugin)OK, I think I need to read this again and test it, at the moment, Hudson has "readonly" access to that repo, this might need to change! :)> > 2) I''m struggling to find a way for puppet 0.25 to perform a "git pull" > > on all > > the master branches _before_ it runs to ensure that the latest configs > > are being distributed. > > Not sure you can, unless you run each client standalone. How about Hudson > invoking something on the puppetmaster when the build passes?Could do. Trying to get away from ssh commands between servers though - although if I used mcollective... I''ll take a look. Cheers, M. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
> I realise that there may not be many who can help with (1), however I''m fairly > sure I''m not alone in using Git for my manifests and I''m wondering how others > get their puppetmaster to always run the latest manifest versions from a git > repo.I have a remote git repo on the puppet master box. The main git repo (running on another box) pushes periodically to the remote repo. Then the puppet master pulls from its local repo and copies the manifests to /etc/puppet/... -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.