On Sun, Oct 28, 2012 at 3:55 PM, Dominic Rodger <dominicrod...@gmail.com>wrote:
> Another long time user here (at some point I'd love to make the jump to > contributor, just need to find more time) - out of interest, is there a > reason we don't use Travis? I wonder if that might help those with commit > access, since pre-tested pull requests would mean you could have confidence > that the tests at least pass. Apologies if this has been discussed before > (there are a few contributors to this group called Travis, which made > searching a bit tricky!). > > We do have a CI server (a Jenkins install) - you can find it here: http://ci.django-cms.org/job/Django/ We don't currently test every fork or pull request on GitHub, but that's certainly an interesting idea, especially if we could get validation that a pull request passes the full test suite. I haven't spent any time messing around with Travis configuration to know how hard this would be to set up -- and whether the build failures can be communicated in an effective way. If you're looking for a way to contribute, investigating the options here might be an interesting place to start. Yours, Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
