15 Aug 2012 01:45
Travis CI
Hello, About Travis: http://about.travis-ci.org/docs/ key facts * It is open source and free to use for open source projects * It use a fresh and disposable VM for each build Examples of big project using Travis: * Node.js: http://travis-ci.org/#!/joyen/node * Ruby: http://travis-ci.org/#!/ruby/ruby I have put a branch of my Contiki fork on Travis just now and it builds `examples/hello-world` for three targets (native, minimal-net and redbee-econotag) the results: http://travis-ci.org/#!/errordeveloper/contiki-work the way it is currently configured: * `.travis.yml` [https://github.com/errordeveloper/contiki-work/blob/3ace4a670e4ec99e7a433d917dcbae34836c1fc5/.travis.yml] * `examples/CI/Makefile` [https://github.com/errordeveloper/contiki-work/blob/3ace4a670e4ec99e7a433d917dcbae34836c1fc5/examples/CI/Makefile] Genrally this demostrates how to configure Contiki to build on Travis with one non-native architecture. I have a few ideas how this current configuration can be improved, i.e. use a wrapper script which will show what examples are currently building okay from each of the architectures and hide compiler output unless error or warning occurred with some colour full indication so it can be linked from Contiki-OS.org as an indicator of stability.(Continue reading)
RSS Feed