#19891: Travis CI support
-------------------------------------+-------------------------------------
Reporter: marko@… | Owner: nobody
Type: | Status: new
Cleanup/optimization | Version: master
Component: Testing framework | Resolution:
Severity: Normal | Triage Stage:
Keywords: Travis, CI, testing | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by jacob):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
I don't think having Travis test all versions is such a good idea. Right
now the build generates 12 different builds for each pull request which'll
take approximately forever to run. Asking people to wait on pull requests
while a dozen different builds run is... not so good.
Instead, how about using Travis to augment what we already have in
Jenkins? Just have it run maybe two builds -- Python 2 and Python 3? That
was contributors can get a quick feedback on a pull request, but don't
have to wait forever.
--
Ticket URL: <https://code.djangoproject.com/ticket/19891#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" 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].
For more options, visit https://groups.google.com/groups/opt_out.
