ingenieux/beanstalker

Split UpdateEnvironment into UpdateEnvironmentConfigurationSettings and UpdateEnvironmentVersion

Closed this issue · 5 comments

akbertram commented

Great!
Hey, what's the definitive source repo? I tried finding it on bitbucket but
got a bit lost (maybe just because i'm not familiar with Hg)

I would suggest splitting update environment into
UpdateEnvironmentConfigurationSettings and UpdateEnvironmentVersion because
you can't do both with the same API call.
Implementation here:
akbertram@f48b60d

This is great, by the way, we're using it now in combination with jenkins
and the maven release plugin to totally automate both nightly builds/deploys
and production releases. Marvelous!

Alex

aldrinleal commented

Alex,

I will split, but in a different manner: update-environment will keep (albeit sans settings), in order to keep regression, and there will be update-environment-options as well. Is it fine for you?

aldrinleal commented

Alex,

I'm closing for now. It is still little documented (update-environment versus update-environment-options), but we hope to improve on docs soon.

also, check the new HOWTO on Continous Integration. I added some very interesting targets for Jenkins users (beanstalker is actually built on Bamboo, but more as a proof-of-concept. I should be moving my projects to Jenkins shortly)

http://beanstalker.ingenieux.com.br/continuous-integration.html

akbertram commented

Great!
The wait-for-environment could very useful to actually verify that a build goes up.

In addition to the continous integration wire up, we're also using beanstalker as part of the maven release process:
https://github.com/akbertram/activityinfo/blob/activityinfo-2.1/sigmah/pom.xml#L830

So now, with Jenkins and the jenkins maven release plugin, performing a release - building, tagging, deploying to maven repository AND launching new environment with new version is a one click operation. Then after manual sign of, we do swap urls through the AWS console. It's magical. Thanks again for your work on this!

aldrinleal commented

Now there is swap-environment-cnames as well, Alex (See latest trunks)

akbertram commented

I saw it! Nice.

On Mon, Jul 25, 2011 at 5:23 PM, aldrinleal <
reply@reply.github.com>wrote:

Now there is swap-environment-cnames as well, Alex (See latest trunks)

Reply to this email directly or view it on GitHub:
#6 (comment)