Difference between revisions of "A Day in the Life of a Checkin"
| Line 9: | Line 9: | ||
[This is a stub since I (Squirrel) didn't have much to add to this discussion. Please add details.] | [This is a stub since I (Squirrel) didn't have much to add to this discussion. Please add details.] | ||
| − | We discussed the synchronous, less-automated continuous integration described by James Shore here: http://jamesshore.com/Blog/Continuous-Integration-on-a-Dollar-a-Day.html. No one had actually tried this CI method, but most did not think it was workable with larger teams and complex tests (such as the acceptance tests described in the next section). | + | We discussed the synchronous, less-automated continuous integration described by James Shore here: http://jamesshore.com/Blog/Continuous-Integration-on-a-Dollar-a-Day.html. No one had actually tried this CI method, but most did not think it was workable with larger teams and complex tests (such as the acceptance tests described in the next section). We also couldn't see how it would work when some team members are remote (or just working from home or a customer site temporarily). See this [http://www.flickr.com/photos/jetbrains_teamcity/2920568933/in/set-72157607811381100/ photo of the board] from this part of the session. |
== CI Real-World Example == | == CI Real-World Example == | ||
We discussed how CI runs at [https://dev.youdevise.com youDevise], a small financial-services firm in London. [Here's a [http://www.flickr.com/photos/jetbrains_teamcity/2920569661/in/set-72157607811381100/ photo of the board]; Diagram and more details to follow shortly.] | We discussed how CI runs at [https://dev.youdevise.com youDevise], a small financial-services firm in London. [Here's a [http://www.flickr.com/photos/jetbrains_teamcity/2920569661/in/set-72157607811381100/ photo of the board]; Diagram and more details to follow shortly.] | ||
Revision as of 19:30, 12 October 2008
Using Git And Friends
[This is a stub since I (Squirrel) didn't have much to add to this discussion. Please add details.]
We discussed using Git, Mercurial, and similar distributed version-control systems. The consensus was that DVCS works best with continuous integration if you have a central repository from which to draw candidates for CI builds. Why use a DVCS then, since it is not necessarily distributed? The tools provide extra flexibility before the commit to the main repository, and have other useful features besides (e.g. Git's whole-tree diffs allow you to track code as it moves from file to file).
Synchronous CI
[This is a stub since I (Squirrel) didn't have much to add to this discussion. Please add details.]
We discussed the synchronous, less-automated continuous integration described by James Shore here: http://jamesshore.com/Blog/Continuous-Integration-on-a-Dollar-a-Day.html. No one had actually tried this CI method, but most did not think it was workable with larger teams and complex tests (such as the acceptance tests described in the next section). We also couldn't see how it would work when some team members are remote (or just working from home or a customer site temporarily). See this photo of the board from this part of the session.
CI Real-World Example
We discussed how CI runs at youDevise, a small financial-services firm in London. [Here's a photo of the board; Diagram and more details to follow shortly.]
