- From: KC Braunschweig <
>
- To:
- Subject: [chef] Re: application deployments
- Date: Thu, 12 Jul 2012 11:25:40 -0700
On Thu, Jul 12, 2012 at 9:13 AM, JayP
<
>
wrote:
>
In addition I wanted to get some suggestions on how best to manage the
>
version
>
number of the application rpm being deployed into qa/staging/production.
>
Since
>
we have a separate continuous integration pipeline for our infrastructure
>
code
>
(cookbooks) and the rev'ing of the cookbook in the production.json file is
>
automated through our CI system I would rather not store the application rpm
Mapping application versions to environments is a good use for a data
bag. At my former company we did this initially and eventually
replaced the data bag with a separate web service that provided
similar data but could run custom business logic to manage version
promotion. This was for deploying maven artifacts (java shop) but a
similar strategy should work for rpm versions. I should bug those guys
about presenting on that stuff someday.
KC
Archive powered by MHonArc 2.6.16.