7. “Continuous integration (CI) is the practice, in
software engineering, of merging all developer
workspaces with a shared mainline several times a day.”
http://en.wikipedia.org/wiki/Continuous_integration
8. It’s a bit like Agile
• It’s a set of 10 principles
• Principles describe techniques
• There are tools to help you do it
• But noone started a war over CI (yet)
9. • Maintain a code repository
• Automate the build
• Make the build self testing
• Everyone commits to the baseline every
day
10. • Every commit (to baseline) should be built
• Keep the build fast
• Test in a clone of the production
environment
• Make it easy to get the latest deliverables
11. • Everyone can see the results of the latest
build.
• Automate Deployment.
Who am I (I use grown up language sometimes) What Code Enigma do What I do with Code Enigma Probably going to talk a bit about how these slides were made, very excited by them
re: How - wanted to do a live walkthrough, unprepared
Originally wanted to do a live walkthrough, no internet access. You’re all left with a crappy slideshow.
So things we SHOULD do, things we ACTUALLY do things we ACTUALLY do this WITH
What I like to call ‘filler’ slides.
Arguably, you should DEVELOP in a clone of the production environment. Actually, no it’s not arguable. Just do it. Save yourself time and pain.
You can tell I discovered the ‘build in’ options here.
What was release day? What was release day *like*? Stressful. Time consuming. Risk. (looking back, it was quite fun, but not for right reasons)
Time = Money How long does it take to build stuff?
Types of risk, and how they’re mitigated with CI tools
