I don't know any scenario like that: usually dependencies are frozen (and tested) separately in a "release". It makes the whole process simpler.
Possibly they wanted to test how far they can push TDD, to be able to do testing on the entire code (apps + libraries) using the development branch (all commits done on it), api changes in the clients breaking the servers… I hope you won't find *any* CI doing that: that'd be very "code specific" nothing that a CI should be aware of :D I hope this helps On 18 May 2013, at 12:36, John Lee <j...@pobox.com> wrote: > Speaking of CI and deployment -- Does anybody know of an open source > implementation of the idea described in this blog post? Maybe somebody has > one and could open-source it? > > http://googletesting.blogspot.co.uk/2011/06/testing-at-speed-and-scale-of-google.html > > > We're not all google, but overkill nicely implemented is sometimes just > convenient and powerful. _______________________________________________ python-uk mailing list python-uk@python.org http://mail.python.org/mailman/listinfo/python-uk
