Great! ----- Original Message ----- | From: "Serge Stinckwich" <serge.stinckwich@gmail.com> | To: "Pharo Development" <pharo-project@lists.gforge.inria.fr> | Sent: Friday, June 8, 2012 2:45:22 AM | Subject: [Pharo-project] Using github & Travis CI for a Smalltalk project | | Hi all, | | I have done some experiments in order to use travis CI for Smalltalk | project hosted on github. | Travis is a free continuous integration service: | http://travis-ci.org/ | that is deeply integrated with github. | | I'm using FileTree repository (thanks to Dale !) to store the code on | github. | Look at this example project here: | https://github.com/SergeStinckwich/PlayerST | I configure Travis continuous integration service to run the tests | everytime i commit on github. | | This is quite easy, you just have to add a .travis.yml script like | this one: | https://github.com/SergeStinckwich/PlayerST/blob/master/.travis.yml | | This script use Builder tools (thanks to Lukas !): | https://github.com/renggli/builder | | This is the result of running the tests: | http://travis-ci.org/#!/SergeStinckwich/PlayerST/builds/1565363 | | At the moment, this is quite rough, because i just print all the | result on the console. | There is room for improvements, but the idea is that every Smalltalk | project could use a continuous integration process like the one used | by Pharo. | | What is really nice is that travis runs also the script for all the | branches and pull request. | So you can imagine, take into account the results of the script | before | doing the integration in the main branch of your dev. | | Cheers, | -- | Serge Stinckwich | UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam | Every DSL ends up being Smalltalk | http://doesnotunderstand.org/ | |