On Fri, Jul 11, 2014 at 9:23 AM, Peter Suter <[email protected]> wrote:
> On 07.07.2014 21:14, Ryan Ollos wrote: > >> On Fri, Jul 4, 2014 at 11:57 PM, Jun Omae <[email protected] >> <mailto:[email protected]>> wrote: >> I just noticed that the mirror repository on github has enabled >> travis-ci testing by someone. See >> https://travis-ci.org/edgewall/trac/builds >> >> We could start testing on travis-ci once we add .travis.yml to each >> branch in subversion repository. >> >> >> That sounds great. I vote for adding the .travis.yml since there is no >> harm and we can always delete it later. >> > > Sounds cool. > > Would it make sense to document / link to this service somewhere on the > wiki? Is this similar to the previous Automatic builds [1] and/or Python > Community Buildbot [2]? (Neither seems to be available anymore. Perhaps > their description should be removed instead.) > > > Cheers, > Peter > > [1] http://trac.edgewall.org/wiki/TracDev/UnitTests#Buildbots > [2] http://trac.edgewall.org/wiki/TracDev/AutomaticBuilds Those look like the right places to document the Travis CI service. It might be good to just remove the section in [1] and add a link from there to [2], updating [2] with new information about Travis CI. I'll plan to update those eventually if you don't beat me to it. It could be nice to have a dedicated mailing list for build notifications. Looking at the current mailing lists [3], the Trac Tickets list is probably too verbose for many people that would be interested in knowing about failing builds. Maybe we could have a [email protected]? [3] http://trac.edgewall.org/wiki/MailingList -- You received this message because you are subscribed to the Google Groups "Trac Development" 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]. Visit this group at http://groups.google.com/group/trac-dev. For more options, visit https://groups.google.com/d/optout.
