Continuous Integration (CI)
Download as PPTX, PDF0 likes360 views
The document discusses continuous integration (CI), which involves having multiple developers working on a project simultaneously in different locations. It notes issues that can arise when there is no standardized process for deploying or fixing applications. It also lists Joel's 12 steps for better code, such as using source control, making daily builds, fixing bugs before adding new code, and using the best tools. Examples are provided of integrating a new team member and a single development iteration using CI.
Continuous Integration (CI)
- 1. Continuous Integration (CI)Eugene Kartsev
- 4. Lots of developers…10 devin Kiev15 QAin NY10 devin Sydney
- 5. Issues:Nobody knows how to deploy/configure the appFixing an issue is very expensive operation
- 6. The Joel Test: 12 Steps to Better Code1. Do you use source control? 2. Can you make a build in one step? 3. Do you make daily builds? 4. Do you have a bug database? 5. Do you fix bugs before writing new code? 6. Do you have an up-to-date schedule? 7. Do you have a spec? 8. Do programmers have quiet working conditions? 9. Do you use the best tools money can buy? 10. Do you have testers? 11. Do new candidates write code during their interview? 12. Do you do hallway usability testing?
- 7. Example: New team player+
- 9. Questions