#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
-------------------------------------+-------------------------------------
Comment (by dokterbob):
There's a pull request now, running the tests:
https://github.com/django/django/pull/805
The tests take 25-45 minutes to run, which is not 'forever' AFAIK. Travis
runs 3-5 builds in parallel which actually makes it fairly fast. However,
somehow, Travis adds up the time for the individual builds to come up with
a rather unrealistic build time of multiple hours.
As the core dev's have a Jenkins CI anyways, this shouldn't matter too
much for them. However, many contributors would benefit tremendously by
being able to test their code throughly even before firing pull requests -
which is the main point of this patch. And lastly, it *might* happen that
Travis finds issues which (somehow) slip through the mazes of the Jenkins
CI, as was the case while we set up the testing system. (Ref:
https://github.com/django/django/commit/8c1cc4b3b04f639ae40bc806380bc4a9dd568eb0)
However, having it run on 4 Python versions might indeed be too much.
Which two Python releases do you suggest we use?
--
Ticket URL: <https://code.djangoproject.com/ticket/19891#comment:2>
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.
