[chef] Re: Re: Re: New to Chef

[Vladimir Girnet < >]

Another way is to use a CI like Jenkins, and have a job that monitor repository for changes and publish them automatically.
This way you will have history of what and when was published.

On 2/8/12 6:12 PM, mark bradley wrote:

" type="cite">Yes, that's exactly what I was asking about -- thanks for the pointer, I'll look at git hooks now :)

Thanks,

Mark

On Wed, Feb 8, 2012 at 11:00 AM, Bryan McLellan < "> > wrote:

On Wed, Feb 8, 2012 at 10:34 AM, mark bradley < "> > wrote:
> Is there a way to have the Chef server detect changes to the backing Git
> repository and cause itself to up updated (whether cookbook, role, node,
> etc. changes)?

I'm not clear on what you're asking.

If you have all your cookbooks and roles and whatnot stores on disk in
a traditional 'chef-repo' you are wondering if Chef could track that
git repo and import objects automatically?

If that's what you're asking, sometimes people have wanted something
where when they push their chef-repo to a central team repository,
they use git hooks there to run the proper knife commands to upload to
the server.

Otherwise, could you provide a fuller example please?

Bryan

-- 
Vladimir Girnet
Infrastructure Engineer
Tacit Knowledge
http://www.tacitknowledge.com