[okfn-labs] Travis CI

Fri Aug 17 06:28:43 UTC 2012

Hi Everyone,

Thanks a lot for the feedback! I use a pre-commit hook in my github repos
to run all the tests before even pushing the code, so I know for sure if
what I'm pushing is broken or not.

This is not the best case scenario as for small commits all the tests are
run too :-) The truth is that this "working mode" has made me to be more
cautious with the code, hehe.

In any case, I think I'll give it a try to Travis.

Cheers,

Daniel

On Thu, Aug 16, 2012 at 7:43 PM, Matthew Brett <matthew.brett at gmail.com>wrote:

> Hi,
>
> On Thu, Aug 16, 2012 at 10:19 AM, Sean Hammond <sean.hammond at okfn.org>
> wrote:
> >> Today I discovered the Travis CI (http://about.travis-ci.org) service
> and I
> >> was wondering if OKFN has some projects using it or if you have your
> own CI
> >> system. I think it would be awesome if OKFN provided something similar
> for
> >> the lab projects :-)
> >
> > I'd be interested too. For CKAN we have a Jenkins instance that we use
> > both to run the unit tests and to build the docs each time a commit is
> > pushed to github, but to be honest it's a real pain to maintain and we
> > don't really have enough spare developer cycles to keep it running, as a
> > result it's broken all of the time and I don't think any CKAN devs look
> > at it.
> >
> > There's just a lot of things that can go wrong, and if CKAN tests are
> > failing on Jenkins, chances are 99% that it's a problem on Jenkins
> > rather than a bug in CKAN, the tests are never 100% passing on Jenkins
> > (i.e. it's pretty much useless). Also Jenkins' default presentation of
> > the test runs it has done doesn't tell you what commit or branch it was
> > testing! Even if you managed to plug all the holes in Jenkins, give a
> > few days and new ones will appear.
> >
> > Perhaps there are some Jenkins best practices out there that we aren't
> > following, and also simplifying and standardising CKAN deployment would
> > help.
> >
> > I understand that buildbot which was previously used for CKAN had the
> > same fate.
> >
> > With Travis CI, I worry that it will have the same problem as using
> > readthedocs for CKAN did, it broke on their end and they didn't fix it
> > or respond to emails, so we just had to migrate off it.
>
> I've had the same experience with Travis CI as Vitor; it was easy to
> set up and had been reliable and very useful:
>
> https://github.com/nipy/nibabel/blob/master/.travis.yml
> https://github.com/nipy/nipy/blob/master/.travis.yml
>
> Having said that, I do put a moderate amount of work into maintaining
> a buildbot instance with many slaves, because we need cross-platform
> testing:
>
> http://nipy.bic.berkeley.edu/builders
>
> Cheers,
>
> Matthew
>
> _______________________________________________
> okfn-labs mailing list
> okfn-labs at lists.okfn.org
> http://lists.okfn.org/mailman/listinfo/okfn-labs
>

-- 
··························································································································································
http://github.com/teleyinex
http://www.flickr.com/photos/teleyinex
··························································································································································
Por favor, NO utilice formatos de archivo propietarios para el
intercambio de documentos, como DOC y XLS, sino PDF, HTML, RTF, TXT, CSV
o cualquier otro que no obligue a utilizar un programa de un
fabricante concreto para tratar la información contenida en él.
··························································································································································
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/okfn-labs/attachments/20120817/cbef6b62/attachment-0002.html>