Timeline for Simple explanation of Continuous Integration
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 18, 2015 at 21:12 | comment | added | Kate Gregory | @DanMoulding if I'm being agile and iterative and whatnot in my part of a larger thing that isn't integrated with what someone else is doing, I'm not doing CI. Heck, you can waterfall and CI. Design it all, code it all, test it all if you want - if everyone is using everyone else's code/schema/file layouts all the time, that's CI even if you're using waterfall. The connection is that without CI you live and die by BDUF because that's your only hope (and it turns out to be a faint hope) of having an integration phase of a reasonable length. Adopting CI allowed us to let go of BDUF. | |
| Mar 18, 2015 at 21:06 | comment | added | Dan Moulding | Interesting. To me, this sounds more like comparing CI to waterfall. But you can use a non-waterfall methodology that avoids these problems (like iterative development) and not use CI. | |
| May 17, 2013 at 16:31 | comment | added | Rhys | Thank you - i've strugged to understand CI before simply because I did not know what the alternative was | |
| May 17, 2013 at 15:40 | history | edited | Kate Gregory | CC BY-SA 3.0 | added 126 characters in body |
| May 17, 2013 at 15:37 | comment | added | icc97 | @OnesimusUnbound I remember getting bumped from VSS to Clearcase ... out of pan into fire. Years later after returning to the same company for drinks, I remember someone laughing at a fellow developer for mentioning this new source control called 'Git', "What do we need another source control system for??". | |
| May 17, 2013 at 14:17 | history | edited | Kate Gregory | CC BY-SA 3.0 | added 686 characters in body |
| May 17, 2013 at 14:10 | comment | added | OnesimusUnbound | We had a similar story in which we upgraded a custom application built on SP 2003 to SP 2007. Using VSS (yes, VSS :), each developer checked out a portion of their file, coded for a week and two, then when we integrated our code, boom, that when the problem started since our code deviated significantly. We fixed the integration problem for a month, and the project rented a hotel to accommodate those who live very far on weekdays. On that day, I learned to integrate code on a daily basis :-) | |
| May 17, 2013 at 12:07 | history | answered | Kate Gregory | CC BY-SA 3.0 |