Hi, following on from the timely Hudson post ;-) I too have been working on continuous integration. I am more interested in identifying & integrating the various bits of plumbing first rather than the build solution itself. I figured the infrastructure needed to be understood first, and there could be value in such an interim solution
To this end I have: -written a simple image builder that updates the image in place. -running remotely on a Linux host I have borrowed access -building PharoCore 1.1 from #11110 onwards -started to publish images at http://pharo.gforge.inria.fr/experimental/ remaining is to rename the core images to unstable and then look at running some tests. This has exposed various issues, mainly image timeout caused by the various dialogs that can popup when filing in code. so 1) if anyone would like to test the integrity of these experimental auto-build images, please do 2) discuss if something in this namespace http://pharo.gforge.inria.fr/<> is suitable for automatic publishing - i am not sure how you automatically create gforge "releases" but for core images perhaps this is not needed 3) find a real server we can run this on, (if this is considered worthwhile). My requirements are Linux + daemontools + vnc server - i can host my solution for a while, we need something strategic then once we have a server I'm happy to look at Hudson or whatever we consider the right tool for doing this. I have also been playing with Mason and sent some feedback to Colin. Like i say, for me the real issues are running a Pharo image completely automated. Cheers, Mike _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
