There's a policy change that landed a few weeks ago (27 nov) worth looking 
into:

The new policy will be as follows:


   1. If the commit occurs on the default branch, then the owners of the 
   repository will be notified.
   2. If the commit occurs on a non-default branch, the author and the 
   committer of the commit who are also owners of the repository will be 
   notified.


http://about.travis-ci.org/blog/2013-11-19-upcoming-email-notification-policy-change/

Also 
django-cms/.travis.yml<https://github.com/divio/django-cms/blob/develop/.travis.yml>
 has 
a complete travis setup, including sqlite, postgres and mysql. Could be of 
inspiration for Django's travis config.
(reproduced from: https://code.djangoproject.com/ticket/19891#comment:32)

Op zaterdag 18 mei 2013 13:43:11 UTC+2 schreef Chris Wilson:
>
> Hi all, 
>
> On Thu, 7 Mar 2013, Jacob Kaplan-Moss wrote: 
>
> > On Mon, Feb 25, 2013 at 4:48 PM, Florian Apolloner 
> > <f.apo...@gmail.com <javascript:>> wrote: 
> >> So all in all I think we could enable travis, 
> > 
> > I agree, +1 from me. 
>
> One issue standing in the way: Travis will try to build any branch without 
> a .travis.yml file as though it was a Ruby project. This will fail. It 
> may generate email notifications too, as they are enabled by default. 
> <https://github.com/travis-ci/travis-ci/issues/902> 
> <https://github.com/travis-ci/travis-ci/issues/414> 
> <https://github.com/travis-ci/travis-ci/issues/1095> 
>
> I think we need to add a .travis.yml file to *every* branch that we might 
> ever commit to (including packaging and stable/1.5.x) to tell Travis not 
> to build it. 
>
> Does anyone have a particular objection to adding this one file to old 
> branches, with minimal contents, e.g: 
>
> # see https://github.com/travis-ci/travis-ci/issues/902 
> branches: 
>    only: 
>      - master 
>      - travisci 
>
> I guess this would only cause problems if anyone's building an old branch, 
> or their own fork of django, in Travis. In which case they'll have to 
> resolve the merge conflict, and again whenever we change the .travis.yml 
> file. 
>
> Cheers, Chris. 
> -- 
> Aptivate | http://www.aptivate.org | Phone: +44 1223 967 838 
> Future Business, Cam City FC, Milton Rd, Cambridge, CB4 1UY, UK 
>
> Aptivate is a not-for-profit company registered in England and Wales 
> with company number 04980791. 
>
>

-- 
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 django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/8c69f179-5ec0-46d9-a00c-831ae9593ce1%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to