- From: howard chen <
>
- To:
- Subject: [chef] Re: How do you use Chef for Release Management?
- Date: Tue, 23 Oct 2012 00:38:06 +0800
Our currently workflow:
1. Jenkins build jar and upload to S3 - a fixed Uri
2. Have a recipe that fetch jar from the Uri and do the deploy. The
machines to be deploy have the role "java-web" for example, then
execute
knife ssh 'role:java-web' 'sudo chef-client'
That's all.
On Tue, Oct 16, 2012 at 6:33 AM, Farzad FARID
<
>
wrote:
>
Hi,
>
>
The use of Chef, or similar software like Puppet or Cfengine, for
>
Configuration Management is an undisputed choice (in my opinion of course!),
>
but what about Release Management?
>
>
An IT facilities management company's architect tried to convince me that
>
tools like Chef are not adequate from handling software releases &
>
deployment (here I'm talking about Java/Tomcat applications) and that we
>
should use their costly proprietary platform instead...
>
>
What is your opinion? Do you use Chef for Release Management, is it the
>
perfect tool in this field too?
>
>
Regards
>
>
--
>
Farzad FARID / Architecte Open Source
>
Pragmatic Source / http://www.pragmatic-source.com
>
Tel : +33 9 72 29 31 85 / Mob : +33 6 03 70 65 46
>
Archive powered by MHonArc 2.6.16.