Hi, On Monday, October 29, 2012 1:29:14 PM UTC+1, Aymeric Augustin wrote: > > We tried moving Django's CI to Travis about 6 months ago. Unfortunately, > Travis' time limit is too low for Django's test suite. We contacted them, > but as of August 6th, we were still waiting for them to increase the limit. > I haven't had any news since then. >
We got it raised enough (I think for all Travis projects now) that the test suite does run (at least most of the times). > Over the last months I've had mixed feedback about Travis and I'm less > enthusiastic than I used to be. The tendency to report failures of their > infrastructure as failed tests is annoying. > Hehe, also arbitrary lock ups etc are not helping (I assume those are fixed/found by now). > The .travis.yml format is simple but it's often difficult to make the > builds run. I've seen many people making series of commits, blindly > attempting to make their code importable, and not always succeeding. If > Django uses a service, it's a strong signal for the community; I can't say > I'm ready to give this signal right now for Travis. > Indeed, in most serious cases you require a few extra bash (or whatever) scripts around it, see my branch https://github.com/apollo13/django/blob/travisci/.travis.yml and the needed config stuff: http://apolloner.eu/~apollo13/django/ -- Currently Selenium is a bit flaky, and I can't figure out why. But overall Django could run on travis (without oracle maybe…) Jenkins isn't perfect and it's painful to maintain. But it does the job and > makes it easy for us to run experiments (eg. pypy, Oracle) or diagnose > failures. We don't have short- or medium-terms plans to stop using Jenkins. > +1, debugging is just hard on travis (although I assume I could download their vm and test locally, but usually local stuff works :( ). We could choose a lightweight route and just enable travis for sqlite to get pull requests tested [Which would be pretty useless for eg postgres patches]. But using Jenkins __and__ Travis-CI to test all combinations on both systems will consume more time than we have. Cheers, Florian -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-developers/-/U5wmTLBEydgJ. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
