Difference between revisions of "CI Antipatterns and Kitchen Sink"
From CitconWiki
Jump to navigationJump to search| Line 2: | Line 2: | ||
* CI Antipatterns article #2: http://www.ibm.com/developerworks/java/library/j-ap03048/ | * CI Antipatterns article #2: http://www.ibm.com/developerworks/java/library/j-ap03048/ | ||
| − | Antipatterns | + | == Antipatterns == |
* Infrequent check-ins | * Infrequent check-ins | ||
* Broken builds | * Broken builds | ||
| Line 15: | Line 15: | ||
* Polluted Environment | * Polluted Environment | ||
| + | |||
| + | == Other Notes == | ||
* Going to a new project and getting to know how it's built (and improving/automating) can help understand software architecture better | * Going to a new project and getting to know how it's built (and improving/automating) can help understand software architecture better | ||
Latest revision as of 07:23, 19 September 2009
- CI Antipatterns article #1: http://www.ibm.com/developerworks/java/library/j-ap11297/
- CI Antipatterns article #2: http://www.ibm.com/developerworks/java/library/j-ap03048/
Antipatterns
- Infrequent check-ins
- Broken builds
- Minimal feedback
- Spam feedback
- Slow machine
- Bloated build
- Bottleneck Commits
- Continuous Ignorance
- Scheduled Builds
- Works on My Machine
- Polluted Environment
Other Notes
- Going to a new project and getting to know how it's built (and improving/automating) can help understand software architecture better
