Development Best Practices for Continuous Deployment Environment

Transcript

1. Development Best Practices
 for Continuous Deployment Environment! Presented by Akhyar Amarullah
 at Engineering Brownbag Session in Onebit
 on Wednesday, March 17th 2015"
2. What is this Continuous Something stuffs?"
3. Why does it matter?" Centralized source.! Being lazy, automate repetitive tasks. 
 Engineers love automation!! Deploying clean build is a must, 
 but often requires extra time.! Reduce silly mistakes in manual steps.! Higher quality delivery with confidence.!
4. But that’s devops engineer’s job, right? 
 Why should I even care? ! Fine fine, I have heard it before. !
6. Why should I even care?" •  Code requires huge efforts to maintain more than to write.! •  Projects change a lot. Sometimes beyond your sanity can handle.! •  Make changing configurations a breeze.! •  Your code is your responsibility. Continuous Deployment compliance is a standard.!
7. Let’s get started!" Ok, I’m convinced now!
8. Everything on branch “master” (or equivalents) 
 should works and deployable.
 ! •  Incremental/small changes are done on feature branches.! •  Version tag your released commits.! •  Commit in small chunks. But not too small.!
9. Don’t commit files containing 
 sensitive information." •  configs/email.php •  onebit.keystore •  DatabaseConfigs.java •  PASSWORD.txt •  Etc. Basically, files with credentials.! •  These configuration files are kept in your own machine. !
10. Use .gitignore •  Environment-specific configuration files! •  Generated files! – *.apk, *.class, build/, gen/, etc! •  Log files! •  OS’ generated craps! – Thumbs.db! – .DS_Store! •  Tip: Use http://gitignore.io to generate one!!
11. Configuration! Don’t hardcode! Don’t hardcode! Don’t hardcode! Don’t hardcode! Don’t hardcode! Don’t hardcode! Don’t hardcode! !
12. Configuration Files! Separate between different environment
 Local VS staging VS production! Your favorite frameworks might have supported it already. Find it out!! Avoid committing sensitive credentials 
 to public repository.!
13. Laravel Sample!
14. Configuration! •  Must be injectable via either:! –  Configuration files! –  Environment variables (e.g. $SERVER_HOST)! •  Don’t forget to document how to configure your projects!!
15. Recaps" Everything on “master” (or equivalents) should works and deployable." Don’t commit files containing sensitive information.! Use .gitignore Separate configuration based on environments.! Document how to configure the project.!
16. Thanks" Akhyar Amarullah! @akhy"