continuous deployment

[Nahum Wild]

anyone do this? recommend any tools for it? tips of what not to do?

we've got some new small apps (moving to SOA) and would like to try this out.

cheers,
nahum

[Malcolm Lockyer]

Hi,

This is a little bit random, but the Ruby Rogues (the podcast) talked
a little bit about this recently -
Episode 062 RR Monitoring with Joseph Ruscio
http://rubyrogues.com/062-rr-monitoring-with-joseph-ruscio/

Essentially they talk about having good metrics can be vital for going
to a continuous deployment type setup. It's very helpful to have a
graph you can watch after deploying and see: oh no, my errors per min
is going up/response time is going down/whatever metric is important
to your business is going down - I need to look into this.

Might be relevant and/or interesting.


-Malcolm

> --
> You received this message because you are subscribed to the Google Groups
> "WellRailed" group.
> To post to this group, send email to wellr...@googlegroups.com.
> To unsubscribe from this group, send email to
> wellrailed+...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/wellrailed?hl=en.

[Nahum Wild]

I've listened to that podcast already, it's pretty interesting.

As we're building new apps we're requiring metrics just like we *cough* require tests. Currently using Redis to track current state of the system then using the below node lib to subscribe to keys and show live changes via websockets.

https://github.com/terrcin/redis-key-pubsub

I've not yet looked into options for continuous deployment yet...

--nahum

[Krasimir Angelov]

If you have CI server already then adding deployment is usually just adding one more step to your build command. Let's say you have Hudson already setup and watching your development branch and your build command is like

bundle install && bundle exec rake db:migrate db:test:prepare spec cucumber

 and you wanna deploy your app to EY (what's the case for us) if tests pass, then you just need to add that to build command:

bundle install && bundle exec rake db:migrate db:test:prepare spec cucumber && ey deploy -e your_env_name_goes_here -m --branch development

"ey deploy" can be "cap deploy" or "git push heroku master" or whatever you use for deployment. Of course you need to setup SSH keys and everything else you may need.

I've tried this for staging environments only cause usually deployment to production may require scheduling with other teams (marketing , support. etc) but this depends on the app itself.

For monitoring we use New Relic, but I see people really love statsd for custom metrics.

K.

[Nahum Wild]

Cool thanks.

in terms of monitoring I'd add scoutapp.com to your list.

--nahum

To view this discussion on the web visit https://groups.google.com/d/msg/wellrailed/-/tk7dfvQvgHMJ.

[Warren Seen]

As well as New Relic, Scout, etc, you could use http://stillalive.com/ to test-drive your app's business-critical path :)

(disclaimer: I work for reInteractive)

[Krasimir Angelov]

Continuous deployment, GitHub style  - https://github.com/blog/1241-deploying-at-github :)

Looks like a little bit complicated process, but given they hired gazillion new developers recently it might be the right way to do it.