Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CI configuration for Django 1.10 #2724

Merged
merged 2 commits into from
Jun 17, 2016

Conversation

m1kola
Copy link
Contributor

@m1kola m1kola commented Jun 16, 2016

See #2723

@m1kola m1kola added this to the 1.6 milestone Jun 16, 2016
Also ddds Django 1.10 into .travis.yaml
@m1kola m1kola force-pushed the ci_configuration_for_django110 branch from f7d7c6a to 349c217 Compare June 16, 2016 11:31
@m1kola m1kola changed the title Ci configuration for django110 CI configuration for Django 1.10 Jun 16, 2016
@gasman
Copy link
Collaborator

gasman commented Jun 17, 2016

Hi @m1kola - I don't think we should run Travis against every permutation of python version, database and elasticsearch, as that will tie up lots of Travis instances and create a long backlog. I would suggest cutting it down to:

py27-dj110-sqlite-noelasticsearch
py27-dj110-postgres-noelasticsearch
py27-dj110-mysql-noelasticsearch
py27-dj110-postgres-elasticsearch
py34-dj110-postgres-noelasticsearch
py35-dj110-sqlite-noelasticsearch
py35-dj110-postgres-noelasticsearch
py35-dj110-mysql-noelasticsearch
py35-dj110-postgres-elasticsearch

@gasman gasman merged commit 408dcbe into wagtail:master Jun 17, 2016
@m1kola m1kola deleted the ci_configuration_for_django110 branch June 17, 2016 09:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants