Automated deployments of applications that are made up of a large number of services (in our case 20) can be hard, especially when there's a large team building them.
Here we discuss various branching strategies, ways to share code between the services, a continuous integration server performing unit tests on individual services & integration tests across all services, preparation of packages and automatic deployment to staging and production.
We will talk about how a CI pipeline, private gem servers, puppet scripts and a mouse-click come together to give us the one-click deployment everyone dreams of.
Srushti Ambekallu has been involved in all areas of a project lifecycle - inception, development, business analysis (& even a bit of project management, but don't hold it against him), all the way to deployment. He has worked with multinational companies & startups. He spent the first few years working on .Net & Java and Ruby projects before going on to co-found C42 Engineering, a Ruby consultancy based out of Bangalore where he now works as a developer. He consults for C42's clients as well as help with it's own product RubyMonk. He's worked with Ruby for close to three years now.
He is the primary maintainer of Goldberg and the author of XStream.net and has contributed features and bug fixes to other projects like Mogli & the Mail gem.
