Hi all,
On Thu, 7 Mar 2013, Jacob Kaplan-Moss wrote:
On Mon, Feb 25, 2013 at 4:48 PM, Florian Apolloner
<f.apollo...@gmail.com> 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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
