Gavin McDonald popped around #avro on IRC today and set up a couple of
The new URL for all of the Avro builders is:
He's still looking at adding support for Python 2.4. The main issue there
is that the Ubuntu build slaves are on 10.04 which no longer has packages
for Python 2.4 or 2.5 officially.
It shouldn't be difficult to add a C++ build. Support is also partially in
place on his end for a Windows build of Avro C, but the Windows port of Avro
C is not in place.
Each of the builders is triggered by a commit to either their respective
lang directory or the share directory.
They all send email on failure to the list (or should). This has been in
place for the C and Python builders since they were set up a couple of
On Tue, Aug 24, 2010 at 12:45 PM, Bruce Mitchener <[EMAIL PROTECTED]
> How would these differ from the various buildbots that we already have
> No one seemed to be interested previously in helping out with the Java or
> other builders, or we'd have them as well.
> - Bruce
> On Tue, Aug 24, 2010 at 12:30 PM, Philip Zeyliger <[EMAIL PROTECTED]>wrote:
>> I went ahead and set up two Hudson jobs for testing AVRO. I decided to go
>> with different jobs for different languages, because commits will often
>> break one, but not the other.
>> I've made the python build send e-mail to avro-dev on failures. I haven't
>> quite got the Java build to work (latest is awk on Solaris being
>> causing a test to fail), so there's no e-mail coming from that build quite
>> If you're a committer, they recently made it so that you can log into
>> with your LDAP credentials (also the same as svn), so feel free to poke
>> -- Philip