[Pharo-project] [Jenkins] State of transition Hudson -> Jenkins
marcus.denker at inria.fr
Wed Jul 6 11:50:28 CEST 2011
State of transition Hudson -> Jenkins
We are slowly (step by step) moving builds from Hudson to Jenkins.
the last days e.g. Coral (the scripting engine), RPackage, Nautilus...
The largest thing to move will be the VM autobuilt... that will be done later.
Jean Baptiste Arnaud started with a setup for regression testing.
"doing something slow"
"run all tests"
get new image
"doing something other"
"run all tests"
The idea here is that this will be used for the following
-> recompile the image
-> decompile and recompile the decompiled code
-> pretty print
-> condense sources
-> condense changes
On the TODO list we have
-> test the compiled VMs by running all tests on all plattforms
-> update the One-click build script with the last good VM
-> update the VM used to do everything with the self-build vm
The goal is of course to have that what we release be build completely
without human intervention, after every commit (either VM source or Image
In addtion, this setup will be available for others to use. This way students
can easily clone the VM source and set up Continuous Integration for their
research Fork. This will than make it far far easier for people to invent cool stuff
that needs VM changes, like e.g. this:
The problem right now is that all the code is "somewhere" and just picking up where the student left
is a huge amount of work... with Git and autbuild, this will get much much better.
(and it simplifies the life of the student a lot... autobuild, easy to track changes in the upstream...)
JB already successfully builds his Handle VM:
So we are getting there.
Marcus Denker -- http://www.marcusdenker.de
INRIA Lille -- Nord Europe. Team RMoD.
More information about the Pharo-project