Hm, I brought up Travis before, it's awesomely active integrated software with a great team (cheers!). They also now have pull request support, so once we switch to Github it will be killer: http://about.travis-ci.org/blog/announcing-pull-request-support/
But ok, if Travis doesn't support some needed features there's probably no use. On Thu, May 10, 2012 at 11:48 AM, Thomas Müller <[email protected]> wrote: > Hi Pascal, > > thanks a lot for targeting this issue. > > We are about to set up out own ci-server using Jenkins. > > Why not travis? > > With Jenkins we can add some additional analysis tools, which travis simply > doesn't support (like JSLint, php_codesniffer ... etc). > In addition to that we will get automated doc generation (e.g. at > api.owncloud.org) and deployment to demo.o.o/dev. > > The required hardware will hopefully arrive soon. > > THX, > > Tom > > -- > Thomas Müller E-Mail: [email protected] > > > Am Donnerstag, dem 10.05.2012 um 11:33 schrieb Pascal d'Hermilly: >> A lot of things can easily break - especially when developing in a pace like >> Owncloud does. It seems that Owncloud could benefit for some automated >> testing of the core features. >> >> Travis-ci is as they say themselves "a hosted continuous integration service >> for the open source community". >> http://about.travis-ci.org/docs/ >> >> I just thought I would bring it up. >> >> Pascal >> _______________________________________________ >> Owncloud mailing list >> [email protected] >> https://mail.kde.org/mailman/listinfo/owncloud > _______________________________________________ > Owncloud mailing list > [email protected] > https://mail.kde.org/mailman/listinfo/owncloud _______________________________________________ Owncloud mailing list [email protected] https://mail.kde.org/mailman/listinfo/owncloud
