Hi, so during the sprints a few people (thanks to everyone involved, sadly enough I can't remember all the names, so I refrain from mentioning an incomplete list) worked on adding and testing travis support to Django which resulted in this ticket: https://code.djangoproject.com/ticket/19891 and the PR: https://github.com/django/django/pull/805 -- The conclusion is that travis-ci seems to have improved quite a bit since I tested it (mainly it got more stable and they have more/faster machines now).
So all in all I think we could enable travis, but I have two questions: * How much bash magic do we want in the .travis.yml file? One option would be to use a separate repo like I did in my initial work: https://github.com/apollo13/django/blob/travisci/.travis.yml (Personally I prefer my approach a bit more since it would keep the git history clean of changes which are only needed to configure travis properly if the baseimage changes etc...) * Any objections to ship a file like the test_ci.py file in the PR (+ the accompaning docs, especially with regard to dj-database-url)? Thx, Florian -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
