I’ve felt the need for this since I put out the CLR version of Ioke, and now I’ve finally managed to make it happen. Even though I’m the only person with commit rights to Ioke so far, it is still good to have continuous integration running, especially since there are at least seven different builds I want to test, 3 on linux and 4 on windows.
I now have two servers running this. They are not public right now – I will post something when the dashboard is up – but the CI server will send notification emails to the ioke-language Google Group with status.
The current setup tests Java 1.5, Java 1.6 on Linux and Windows. It tests Mono on Linux and Windows, and .NET on Windows.
As a CI server I’m using Cruise, ThoughtWorks own Continuous Integration server. Cruise is a commercial product, but open source projects can use it for free. I’m very happy about it from earlier projects, which is why I decided to use it for Ioke.
ThoughtWorks also gave me two virtual machines to run this CI server – which I’m very grateful for.
2 Comments, Comment or Ping
Hey Ola, do you plan to include a setup for the Apple JVM and/or SoyLatte?
June 28th, 2009
hey is that a joke ? another language, it’s as if we don’t have enough languages around?
If we need to create another language again, that means we are doing thing fundamentally wrong, with the way all languages are created so far.
I will create another language called JOKE, oh while we are on a roll, why not create a new human’s lanugage as well, because English is not good enough for my use ? JOKGLISH is what I will call it , and I hope Governments in many parts of the world will maike JOKGLISH their national language . i will give hugo chavez a call, ‘cos I think he will most likely use that in his country and this will be a good PR for JOKGLISH
July 4th, 2009
Reply to “Continuous Integration for Ioke with Cruise”