Buildbot!

SDL Development
1

So I made good on my threat and set up a buildbot.

Now every change that goes into the main repo is automatically pushed
through as many different build systems as possible. This will help with
concerns that a fix for one platform will break another, because we’ll
know within a few minutes.

Currently we’ve got Linux (x86 and amd64), Mac OS X (x86/amd64/ppc from
the configure script, x86/amd64 through Xcode), Windows (vs2005 and
vs2008…x86 only atm), iOS, Cygwin (gcc3), mingw (gcc4, x86 and amd64),
with more to come.

You can see the “waterfall” (which is a timeline of activity and
results) here:

 http://buildbot.libsdl.org/waterfall

You can subscribe to failure alert emails from buildbot here…

http://lists.libsdl.org/listinfo.cgi/buildbot-libsdl.org

…and there’s an RSS feed, too.

There’s lots to be done still: I haven’t hooked up any tests, including
Markus’s GSoC work, yet…I need to set up Android, Haiku, etc
builders…I don’t have it look at anything but SDL itself (no mixer,
image, etc).

If you’re bored and looking to contribute to SDL, look for things to
turn red in buildbot. These are the most immediate needs, because it
means something is broken Right Now. As you might notice, some things
are red currently.

–ryan.

2

Very nice.On Fri, Sep 9, 2011 at 12:33 PM, Ryan C. Gordon wrote:

So I made good on my threat and set up a buildbot.

Now every change that goes into the main repo is automatically pushed
through as many different build systems as possible. This will help with
concerns that a fix for one platform will break another, because we’ll know
within a few minutes.

Currently we’ve got Linux (x86 and amd64), Mac OS X (x86/amd64/ppc from the
configure script, x86/amd64 through Xcode), Windows (vs2005 and vs2008…x86
only atm), iOS, Cygwin (gcc3), mingw (gcc4, x86 and amd64), with more to
come.

You can see the “waterfall” (which is a timeline of activity and results)
here:

? ?http://buildbot.libsdl.org/waterfall

You can subscribe to failure alert emails from buildbot here…

? http://lists.libsdl.org/listinfo.cgi/buildbot-libsdl.org

…and there’s an RSS feed, too.

There’s lots to be done still: I haven’t hooked up any tests, including
Markus’s GSoC work, yet…I need to set up Android, Haiku, etc builders…I
don’t have it look at anything but SDL itself (no mixer, image, etc).

If you’re bored and looking to contribute to SDL, look for things to turn
red in buildbot. These are the most immediate needs, because it means
something is broken Right Now. As you might notice, some things are red
currently.

–ryan.

SDL mailing list
SDL at lists.libsdl.org
http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org

3

If you’re bored and looking to contribute to SDL, look for things to turn
red in buildbot. These are the most immediate needs, because it means
something is broken Right Now. As you might notice, some things are red
currently.
Should these fixes be submitted as bug reports? For example, the Mac
OS failure seems to result from sail.bmp being missing.

Great work,

John

4

wow. impressive work Ryan!

5

Awesome!On 9/9/11 2:33 AM, Ryan C. Gordon wrote:

So I made good on my threat and set up a buildbot.

Now every change that goes into the main repo is automatically pushed
through as many different build systems as possible. This will help
with concerns that a fix for one platform will break another, because
we’ll know within a few minutes.

Currently we’ve got Linux (x86 and amd64), Mac OS X (x86/amd64/ppc
from the configure script, x86/amd64 through Xcode), Windows (vs2005
and vs2008…x86 only atm), iOS, Cygwin (gcc3), mingw (gcc4, x86 and
amd64), with more to come.

You can see the “waterfall” (which is a timeline of activity and
results) here:

http://buildbot.libsdl.org/waterfall

You can subscribe to failure alert emails from buildbot here…

http://lists.libsdl.org/listinfo.cgi/buildbot-libsdl.org

…and there’s an RSS feed, too.

There’s lots to be done still: I haven’t hooked up any tests,
including Markus’s GSoC work, yet…I need to set up Android, Haiku,
etc builders…I don’t have it look at anything but SDL itself (no
mixer, image, etc).

If you’re bored and looking to contribute to SDL, look for things to
turn red in buildbot. These are the most immediate needs, because it
means something is broken Right Now. As you might notice, some things
are red currently.

–ryan.

SDL mailing list
SDL at lists.libsdl.org
http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org

6

Should these fixes be submitted as bug reports? For example, the Mac
OS failure seems to result from sail.bmp being missing.

Bug reports, patches to the mailing list…usually these things tend to
be small, simple fixes, so anywhere is fine.

–ryan.

7

…I need to set up Android, Haiku, etc builders…

There’s a Haiku builder in there now, but note that the build fails
because I haven’t merged Nathan’s GSoC work yet.

–ryan.

8

awsome work Ryan!On Fri, Sep 9, 2011 at 11:33 AM, Ryan C. Gordon wrote:

So I made good on my threat and set up a buildbot.

Now every change that goes into the main repo is automatically pushed
through as many different build systems as possible. This will help with
concerns that a fix for one platform will break another, because we’ll know
within a few minutes.

Currently we’ve got Linux (x86 and amd64), Mac OS X (x86/amd64/ppc from the
configure script, x86/amd64 through Xcode), Windows (vs2005 and vs2008…x86
only atm), iOS, Cygwin (gcc3), mingw (gcc4, x86 and amd64), with more to
come.

You can see the “waterfall” (which is a timeline of activity and results)
here:

? ?http://buildbot.libsdl.org/waterfall

You can subscribe to failure alert emails from buildbot here…

? http://lists.libsdl.org/listinfo.cgi/buildbot-libsdl.org

…and there’s an RSS feed, too.

There’s lots to be done still: I haven’t hooked up any tests, including
Markus’s GSoC work, yet…I need to set up Android, Haiku, etc builders…I
don’t have it look at anything but SDL itself (no mixer, image, etc).

If you’re bored and looking to contribute to SDL, look for things to turn
red in buildbot. These are the most immediate needs, because it means
something is broken Right Now. As you might notice, some things are red
currently.

–ryan.

SDL mailing list
SDL at lists.libsdl.org
http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org