Travis CI support
|Reported by:||marko@…||Owned by:||gcc|
|Severity:||Normal||Keywords:||Travis, CI, testing|
|Cc:||mathijs@…, apollo13||Triage Stage:||Someday/Maybe|
|Has patch:||yes||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
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.
@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.
Work on this topic is currently being done at https://github.com/dokterbob/django
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
Change History (36)
comment:1 Changed 3 years ago by jacob
- Needs documentation unset
- Needs tests unset
- Patch needs improvement unset
comment:5 Changed 3 years ago by dokterbob
- Cc mathijs@… added
- Has patch set
- Owner changed from nobody to dokterbob
- Status changed from new to assigned
Changed 3 years ago by aaugustin
comment:20 Changed 3 years ago by anonymous
- Owner dokterbob deleted
- Status changed from assigned to new
comment:35 Changed 2 years ago by timo
- Resolution set to wontfix
- Status changed from assigned to closed