Hi Dale: On 20 Feb 2013, at 16:15, Dale Henrichs wrote:
I have to admit that I haven't kept up with Pharo2.0 since last summer when I couldn't use Pharo2.0 for development because of OsProcess issues. I know that recently those issues have been cleared up, but I haven't had the time to return to Pharo2.0 and check things out (I'm facing more issues with getting PHaro2.0 to work with travis-ci, etc. so it will be a big undertaking for me to fully support Pharo2.0).
I have a working build with Travis. Well, working in the sense that it executes my unit tests. The tests actually fail for other reasons. See https://travis-ci.org/smarr/LibGit I use basically the CI infrastructure provided by Pharo 2.0. Guess that's Camillo's work. https://github.com/smarr/LibGit/blob/master/.travis.yml I happen to use a makefile: libgit.image: latest.image $(NBCOG) -headless $< config http://smalltalkhub.com/mc/StefanMarr/LibGit/main ConfigurationOfLibGit --install=bleedingEdge mv latest.image libgit.image mv latest.changes libgit.changes LibGit-Core-Tests-Test.xml: libgit.image $(NBCOG) -headless $< test --junit-xml-output LibGit-Core-Tests The only problem for the build status is to report the correct error code to travis, I think. As I understand it, Travis doesn't actually care about parsing or understanding test results, which is a pity. Best regards Stefan -- Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr Phone: +32 2 629 2974 Fax: +32 2 629 3525