Unfortunately, I have had almost no time to work on this. Unexpected family related emergency put me on finding a job sooner than I thought I'd need to.
If there's anyone here who wants to race me to continuous integration for Squeak now, I will be glad to lose this race, as I really believe that this is something we need sooner than later.
It would also be great to see folks collaborate on a solution; sadly, this shouldn't be too hard, but I just don't have any time. Thus my general absence from squeak-dev, etc.
There are a number of CI-related packages on squeaksource, have you looked at any of these Hannes? I was investigating those when disaster struck. I found at least four different CI-related packages. I would rather not reinvent the wheel unless the wheel is quite broken, but I didn't get as far as actually trying to use these packages.
Hannes, you do great work with regard to investigating various aspects of a problem and summarizing them. Would you like to help me get this part done?
Most likely, and honestly, our best plan is probably to adapt the work that various awesome people have already done.
This one is Igor's:
http://www.squeaksource.com/CISupport
This one belongs to Laurent Laffont:
http://www.squeaksource.com/ContIntegration
This one seems to be a collaboration between Yanni Chiu and Lukas Renggli; we might pay extra attention to this one, because for some reason I think it's what they're using for Pharo presently (though I may be wrong, don't recall why I think this) which means it's been working in production use:
http://www.squeaksource.com/HudsonBuild
And last but not least, here's another one worth looking at, a la Andreas Raab:
http://www.squeaksource.com/InT
My plan was to take a survey of these, contact the maintainers, weigh the pros and cons, and report back to the list. If there was consensus around one of them, I'd run with that, if there wasn't, I would reinvent the wheel.
Thanks for lighting a fire up under my ___, Hannes :D
Everyday life so often distracts from the things that really matter, like Squeak!
On Tue, Sep 6, 2011 at 2:00 AM, H. Hirzel hannes.hirzel@gmail.com wrote:
Are there any news about setting up CI?
--Hannes
<biiiiig snip>
On 07/09/11 2:47 PM, Casey Ransberger wrote:
This one seems to be a collaboration between Yanni Chiu and Lukas Renggli; we might pay extra attention to this one, because for some reason I think it's what they're using for Pharo presently (though I may be wrong, don't recall why I think this) which means it's been working in production use:
That version was the original starting point. I don't maintain or update it, anymore - is there a standard way to mark a package obsolete?
The package was evolved by Lukas and Philippe Marschall, and is found at:
http://source.lukas-renggli.ch/hudson.html https://github.com/renggli/builder
IIUC, it is actively maintained, and is the basis of what runs the Pharo CI builds.
My plan was to take a survey of these, contact the maintainers, weigh the pros and cons, and report back to the list. If there was consensus around one of them, I'd run with that, if there wasn't, I would reinvent the wheel.
Do the analysis if you want, but IMHO, you should just go with whatever is working for Pharo, and save the CI analysis effort for Squeak coding. All you need to start, is a place to run Hudson/Jenkins, a Squeak VM, a shell script to run the image used for the build, and a set of Squeak start-up .st files that controls what gets loaded and/or tested.
A very old setup is at: http://hudson.jooshr.org/job/Squeak4.1/ I've disabled the CI job for some time now (last build was April 2010). The comment says: "Build disabled, since it does not run in headless mode anymore. Have not figured out the problem yet."
The community has to agree that the CI build is the top priority. If the build fails, there is no higher priority item than getting the build to work again. I'm sure that will happen, once the CI build job is setup and running.
Thanks Yanni, yes I noticed that there was a note on the SS page pointing at Lukas' personal SS setup. I pulled the latest from there and am exploring it now.
C
On Thu, Sep 8, 2011 at 7:30 AM, Yanni Chiu yanni@rogers.com wrote:
On 07/09/11 2:47 PM, Casey Ransberger wrote:
This one seems to be a collaboration between Yanni Chiu and Lukas Renggli; we might pay extra attention to this one, because for some reason I think it's what they're using for Pharo presently (though I may be wrong, don't recall why I think this) which means it's been working in production use:
http://www.squeaksource.com/**HudsonBuildhttp://www.squeaksource.com/HudsonBuild
That version was the original starting point. I don't maintain or update it, anymore - is there a standard way to mark a package obsolete?
The package was evolved by Lukas and Philippe Marschall, and is found at:
http://source.lukas-renggli.**ch/hudson.htmlhttp://source.lukas-renggli.ch/hudson.html https://github.com/renggli/**builder https://github.com/renggli/builder
IIUC, it is actively maintained, and is the basis of what runs the Pharo CI builds.
My plan was to take a survey of these, contact the maintainers, weigh
the pros and cons, and report back to the list. If there was consensus around one of them, I'd run with that, if there wasn't, I would reinvent the wheel.
Do the analysis if you want, but IMHO, you should just go with whatever is working for Pharo, and save the CI analysis effort for Squeak coding. All you need to start, is a place to run Hudson/Jenkins, a Squeak VM, a shell script to run the image used for the build, and a set of Squeak start-up .st files that controls what gets loaded and/or tested.
A very old setup is at: http://hudson.jooshr.org/job/**Squeak4.1/http://hudson.jooshr.org/job/Squeak4.1/ I've disabled the CI job for some time now (last build was April 2010). The comment says: "Build disabled, since it does not run in headless mode anymore. Have not figured out the problem yet."
The community has to agree that the CI build is the top priority. If the build fails, there is no higher priority item than getting the build to work again. I'm sure that will happen, once the CI build job is setup and running.
squeak-dev@lists.squeakfoundation.org
-
Casey Ransberger -
Yanni Chiu