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.
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. 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. 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. Finally, I'd like to thank Divio AG <https://www.divio.ch/> for funding the server that hosts ci.djangoproject.com. -- Aymeric. 2012/10/29 Marko Tibold <ma...@tibold.nl> > Hi all, > > I can really recommend travis. We use it for testing Django REST > Framework. The config can be as simple as this > https://github.com/tomchristie/django-rest-framework/blob/restframework2/.travis.yml > > The availability of the travis service is not 100 %, this is mainly due to > the very large amount of OSS projects (5000+) that rely on the service. But > whenever downtime occurs, the problems tend be solved quickly and status > reports are sent via twitter. > > Marko > > On Sunday, October 28, 2012 4:57:01 PM UTC+1, dstufft wrote: > >> Travis or Jenkins can be setup to test PR's and use Github's API to >> mark the PR as good to merge or not. >> >> On Sunday, October 28, 2012 at 5:20 AM, Russell Keith-Magee wrote: >> >> >> On Sun, Oct 28, 2012 at 3:55 PM, Dominic Rodger <domini...@gmail.com>wrote: >> >> Another long time user here (at some point I'd love to make the jump to >> contributor, just need to find more time) - out of interest, is there a >> reason we don't use Travis? I wonder if that might help those with commit >> access, since pre-tested pull requests would mean you could have confidence >> that the tests at least pass. Apologies if this has been discussed before >> (there are a few contributors to this group called Travis, which made >> searching a bit tricky!). >> >> >> We do have a CI server (a Jenkins install) - you can find it here: >> >> http://ci.django-cms.org/job/**Django/<http://ci.django-cms.org/job/Django/> >> >> We don't currently test every fork or pull request on GitHub, but that's >> certainly an interesting idea, especially if we could get validation that a >> pull request passes the full test suite. >> >> I haven't spent any time messing around with Travis configuration to know >> how hard this would be to set up -- and whether the build failures can be >> communicated in an effective way. If you're looking for a way to >> contribute, investigating the options here might be an interesting place to >> start. >> >> Yours, >> Russ Magee %-) >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Django developers" group. >> To post to this group, send email to django-d...@**googlegroups.com. >> To unsubscribe from this group, send email to django-develop...@** >> googlegroups.com. >> >> For more options, visit this group at http://groups.google.com/** >> group/django-developers?hl=en<http://groups.google.com/group/django-developers?hl=en> >> . >> >> >> -- > 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/-/ddqnV4W690IJ. > > 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. > -- You received this message because you are subscribed to the Google Groups "Django developers" group. 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.
