[Labs-l] Self Hosted puppetmaster with puppet clients?

[Andrew Otto]

Hm, its not so hard for me to switch branches on the cloned puppet repo once it is at /var/lib/git/operations/puppet.

> In development cycles, you clone the
> production repository to GitHub or wherever, test changes
> and commit, then, when your changes are merged in Gerrit
Interesting?  Why the need to clone the repo to Github?  (I did that once too :p ).

Is it possible to push directly to an operations/puppet branch, or does every commit have to go through Gerrit review?  I think to make this workable we'd need to be able to push to a branch directly.



On Apr 3, 2013, at 6:26 PM, Tim Landscheidt <tim at tim-landscheidt.de> wrote:

> Ryan Lane <rlane32 at gmail.com> wrote:
> 
>>> Oh totally, branch fo sho.  Then I wouldn't have to git review all the
>>> commits, just squashed commits back to production branch.
> 
>>> But, Ryan you avoided the questions! :)  Maybe this just hasn't been done
>>> before.  May I try?
> 
>> puppetmaster::self would need to be modified for this, or another class
>> would need to be made for it. It's not been done yet.
> 
> I think I dropped this idea somewhere already, but I think
> it would be nice if puppetmaster::self accepted a parameter
> that links to a Git repository and branch and took the con-
> figuration from there.  In development cycles, you clone the
> production repository to GitHub or wherever, test changes
> and commit, then, when your changes are merged in Gerrit and
> you have achieved a more stable configuration, you point
> back to the production repository so that the instance pulls
> any updates from there without having to tear down/create
> new instances.
> 
> Tim
> 
> 
> _______________________________________________
> Labs-l mailing list
> Labs-l at lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/labs-l