On Tue, Feb 10, 2009 at 9:43 AM, Ville Voutilainen
>> Erik Huelsmann wrote:
>>>> Well, since you ask, we'd provide an even better service if we'd avoid
>>>> regressions to begin with. After all, we have enough regression tests,
>>> Mea culpa...
> It's not a big problem, this is the svn HEAD and such breakage is
> bound to happen.
While breakage is to be expected when doing larger-impact changes
(like the stuff where I have started inline support for float and
double Java types), I'm quite a bit ashamed with the (min 1 2 3)
breakage, because it was something too simple.
> We could try and adopt a "ask questions first, file tickets later"-policy too.
I think that would be a good idea: only we can file tickets anyway.
>> A good solution might be some sort of "continuous build server" that would
>> watch the SVN tree, build the tree, run the tests, then publish the results.
>> In Java-land, the current fashion for such software is probably exemplified
>> by Hudson. Perhaps we could get some sort of server space "donated" by
I have a VPS at tech.coop, but it's already running a testing server.
It also has too little memory (128MB) to run anything Java based.
Upgrading the account doesn't cost much, but the charge is monthly...
If anybody wants to sponsor the additional charge (ca 30 CAD [a little
bit less than 20 EUR], I think for an upgrade to 512MB).
> Some people also use CruiseControl, AFAIK. Hmm, maybe I should ask my
> company (1) if they're willing to provide such a build service. In the mean time,
> other possibilities for this should definitely be investigated, the company bureaucracy
> takes its time.
> There's also some amount of risk involved if such a build service is
> hosted by any company, but it's one option.
True, but as long as we have a copy of the configuration files, I
don't see much problems with it: we should be able to relocate the
service anywhere quite quickly..
> (1) my employer states that they're willing to provide "environments
> and infrastructure"
> for open-source projects participated in by employees. The exact
> meaning of that is not very clearly defined, as it's a work-in-progress, but I'd think a
> nightly build service would fit into that description.
Although bureaucracy usually is a bit slow, I don't think that - when
being offered - we shouldn't give it a try: We currently don't have
anything and - at least I - don't have other options.
However, since your company already sponsors your hardware, I'll post
separately on the subject of sponsoring our project. Especially if
we're going to see commercial users, I think it's only fair to ask for
something back which will benefit our productivity or the larger
community in general.