[Vm-dev] Hudson Status?

Nicolas Cellier nicolas.cellier.aka.nice at gmail.com
Wed May 4 05:45:37 UTC 2011


2011/5/4 Igor Stasenko <siguctua at gmail.com>:
>
> On 4 May 2011 03:39, Casey Ransberger <casey.obrien.r at gmail.com> wrote:
>>
>> Hello all,
>>
>> I have chunk of free time coming up, and a bunch of professional experience with CI. Seems I end up being the guy who sets it up and drives the effort wherever I go.
>>
>> Curious where the status for the Hudson effort is. Is the blocker mostly time? I should be able to get it done, if so.
>>
>> I'm interested in doing both VM-level and image-level CI. If you're currently working on the Hudson effort for Squeak, please let me know so that I don't have to duplicate your efforts.
>>
>
> Thank you, Casey for willing to help.
> Hudson status: up and working. And most of the times it does its job.
> Except that we would like a more finer control on it.
>
> Currently Hudson are set up for us by INRIA engineers, and while it
> was good from the beginning (we don't need to spend time setting up
> things by ourselves), today our demands looks like outgrew what admins
> at INRIA could propose :)
>
> We will have a meeting on this week and discuss our problems.
> We're certainly want to have more open access to servers by community
> members, so they could set up, configure and run their own jobs.
> Stef says that he want servers to burn in flames (means busy with
> always building something).
>
> But we meet some organizational/political problems we need to overcome first.
>
> I think Stephane could say more about it.
>
>
> What help i personally might need? Well.. building VMs on many various
> platforms and making working cmake configs for them.
> So, mainly its about creating and testing new cmake configurations.
>
> Oh.. yeah.. we would like to set up a benchmarking suites for running
> benchmarks after each VM build. And then outputting results to some
> file(s), so we can detect performance regression from build to build
> etc etc.
> That would be really nice.
> But that means some coding, because first we need to create some kind
> of benchmarking suite, and also some layer to output results, which
> hudson can understand (expect heavy xml resistance ;)
>

About bench, I would begin with what's already there, the shootout.
Eliot used it.

Nicolas

>
> --
> Best regards,
> Igor Stasenko AKA sig.
>


More information about the Vm-dev mailing list