Flipkart.com is one of India's top 100 websites in terms of traffic. We use continuous deployment techniques to achieve quick deployments multiple times a day. Techniques and best practices we follow that we believe could be interesting to many others.

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

3. Point docroot to new svn

4. Place copies on all servers

5. One server at a time

6. Check if it works

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.

12. or

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

14. Flipkart releases

17. Step2: there is no Step 2

19. You don't need magic

30. It's a philosophy

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

34. Subversion

35. SSH

36. Puppet

39. Integration Environments

40. Packaging

41. Configuration

42. Automated Builds and Deployments

45. Step 2: build feature/ fix bug

46. Step 3: Commit to mainline/trunk

49. Integration Environments

50. Packaging

51. Configuration

52. Automated Builds and Deployments

56. ENG is on virtual machines

59. initiates a build

60. notifies the committer of the result of the build

62. Integration Environments

63. Packaging

64. Configuration

65. Automated Builds and Deployments

68. All software is installed using apt-get

70. .deb pushed to a repository (flipkart repo)

72. Version information

73. Allows rollbacks and prevents software mismatches

74. Apt Repository

75. Apt Repository

77. Integration Environments

78. Package management

79. Configuration

80. Automated Builds and Deployments

84. properties files

85. database schema

86. install scripts

87. third party libraries

90. Integration Environments

91. Packaging

92. Configuration

93. Automated Builds and Deployments

97. One or more to run secondary tests (sandbox)

99. Deployment procedure is the same everywhere

101. Contains Build scripts for all packages for all env

102. Monitors the svn tree for changes

103. Build new packages automatically (or manually)

104. Deploys new packages automatically (or manually)

107. Builds succeed in all test environments

108. Elaborate test cases

109. Automatically hit production

111. Some teams use Teamcity to do integrated builds on every commit

112. We can do continuous deployments till prod but we do not practice it in every project

115. Sandbox to do smoke tests

116. Functional tests before push to production

118. martinfowler.com

120. Spo0nman on freenode #linux-india #perl #debian