The document outlines Flipkart's continuous deployment process, which emphasizes integrating frequently, using multiple environments, and automating builds and deployments. It highlights the importance of having a streamlined deployment procedure without unnecessary steps, ensuring that all necessary artifacts are included in the repository. The goal is to enable a stable and rapid deployment cycle while minimizing downtime and errors in production environments.

1. Continuous deployment at flipkart Pankaj Kaushal Photo credit: http://www.flickr.com/photos/bomb_tea/

2. Old school deployment Check out svn

3. Point docroot to new svn

4. Place copies on all servers

5. One server at a time

6. Check if it works

7. Fear of the tar Site breaks unexpectedly

8. many downtimes everyday

9. most related to deployments

10. Deployments Module X is no longer working. Foostat widget is now displaying php instead of rendering html. All images are gone Blah blah tab shows sometimes and disappears sometimes I get blank screens I'm sure I deployed on all four servers Forgot to restart foo backend service If anything can go wrong, it will.

11. Discourage deployments in the interest of stability?

12. or

13. Allow deployments to happen as fast as they need to?

14. Flipkart releases

15. Deployment should be a non-event

16. Flipkart deployment procedure Step1: svn copy -m “ deploying to prod ” trunk/ prod/2011-07-08-10:00/

17. Step2: there is no Step 2

18. How?

19. You don't need magic

20. 1. Continuous integration

21. 1. Continuous integration integrate frequently against a controlled source code repository Multiple integrations per day

22. 2. Multiple Environments

23. 2. Multiple Environments Integration environments are replicas of production All components of the system are available Duplicate the production environment as much as you can

24. 3. One step build

26. 4. One step build and deploy

29. Continuous integration Is not a tool, neither is it the result of a tool

30. It's a philosophy

31. You don't need lots of money or fancy tools

32. We use a bunch of shell scripts to do this

33. Use existing Free software Debian

34. Subversion

35. SSH

36. Puppet

38. Continuous integration

39. Integration Environments

40. Packaging

41. Configuration

42. Automated Builds and Deployments

44. Building with Continuous Integration Step1: check out trunk/mainline

45. Step 2: build feature/ fix bug

46. Step 3: Commit to mainline/trunk

47. Step 4: Commit to eng/ Integration environment builds automatically

48. Continuous integration

49. Integration Environments

50. Packaging

51. Configuration

52. Automated Builds and Deployments