- From: KC Braunschweig <
>
- To:
- Subject: [chef] Re: Re: Re: Re: Re: application deployments
- Date: Fri, 13 Jul 2012 13:19:18 -0700
On Fri, Jul 13, 2012 at 5:56 AM, Jay Perry
<
>
wrote:
>
And also a follow up to the CI Server, when you build a newer version of
>
your application did you have your CI server check in the data bag before
>
pushing to the chef server? Did you ever run into any issues with this
>
approach?
The databag based solution was gone before it mattered. However this
should be manageable. The CI server creates your versioned artifact
and puts it in a repo (maven artifacts in nexus in our case). This
should always happen first. You make the version available but nothing
will use it. Then you update your databag or whatever to tell an
environment to use the new version you made available. No node takes
action based on the repo so the only thing to work around is what if
your upload of the data bag fails? You probably can start with manual
intervention at that point because you have a bug in your CI code
generating a bad databag item or your chef server is hosed and you
have bigger problems.
KC
Archive powered by MHonArc 2.6.16.