#19891: Travis CI support
--------------------------------------+---------------------------------
Reporter: marko@… | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Testing framework | Version: master
Severity: Normal | Keywords: Travis, CI, testing
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+---------------------------------
= Use cases =
== Standardizing testing ==
Contributors test their own changes against all different databases and
supported python versions and testing is standardized.
This means they do not have to setup configure and maintain multiple
database setups, install multiple python versions etc.
== Pull requests get tested automatically ==
This gives core-devs a first impression on the quality of a patch.
= History =
@apollo13 has made some initial attempts at supporting Travis CI, but
stopped working on this
because the tests were taking too long and were causing timeouts. New work
being done is based
on his initial attempts.
= Development =
Work on this topic is currently being done at
https://github.com/dokterbob/django
= Discussion =
Not everyone is too fond of travis-ci. Sometimes people tend to pollute
the commit history with commits just to
trigger Travis CI.
The work being done is not to replace Jenkins CI. It is only intended to
improve and standardize testing of Django by
none-core developers.
--
Ticket URL: <https://code.djangoproject.com/ticket/19891>
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.
