How to use the Xuggler/Red5 Build Server

Hi Folks,

The tip of tree of Xuggler and Red5 went through some instability yesterday for a few reasons:
1) Googlecode went down hard several times causing builds to be aborted.
2) FFmpeg added a memory leak (when we get a memory leak, we fail a build since Java doesn't handle even small leaks well).  We submitted a patch to FFmpeg and they incorporated that this morning.
3) In attempting to fix a Mac JVM issue with Xuggler biting one of our users, I broke the Xuggler Windows install (which given that it takes 2+ hours for a windows build, I didn't notice).
4) And, um, there might be a feature or two getting added for Xuggler 3.1, and some refactoring occuring in Red5 that caused failures.

We're getting those issues ironed out, and this is normal and to be expected in the source of developing open source software.  For Xuggler, I expect the 'instability' to continue throughout this week because of reason #4 abov.

That said, based on some questions I got yesterday, I thought users might appreciate a tutorial in how to use http://build.xuggle.com/

1) If Red5 or Xuggler releases an official version, you should consider that the best version to use.  Period.
  a) Red5 Official Releases: http://code.google.com/p/red5/ (but will  move to http://www.red5.org "soon").
  b) Xuggler Official Releases: http://www.xuggle.com/xuggler/downloads

2) If you for some reason want newer versions, use the build server: http://build.xuggle.com
  a) If a build shows up on the "Stable page" and is Green or Blue, that means it passed all tests on all JDKs (including memory leak, system checks, and load tests): http://build.xuggle.com/view/Stable/
  b) If a build shows up on the main page, and it is Green or Blue, that means it passed all tests in that build, but each sub-build only does certain tests.  The actual build may not be good to use.
  c) If a build shows up as Red5 or yellow, it's unstable.  Don't use it.  Period.
  d) Bear in mind, even if the build is marked stable on the build server, it's not an official release.  Use at your own risk.

3) If you want a quick view of the relative "build health" of the Red5 or Xuggler projects, you can use the Dashboard views:
  a) Red5: http://build.xuggle.com/view/Red5%20Dashboard/
  b) Xuggler: http://build.xuggle.com/view/Xuggle%20Dashboard/
  Failing builds will show up first.  If a build is Blue it means it's stable.  You'll notice we're still recovering from all the failures yesterday, but I expect you'll see nice dashboards of blue by tomorrow morning.

4) If you'd like RSS feeds of all build results, click on the RSS icons for the build you care about.  See http://build.xuggle.com/

5) Finally, if you'd like to get feedback on all check-ins going into either Red5 or Xuggler, there are RSS feeds for those too:
  a) Red5: http://code.google.com/feeds/p/red5/updates/basic
  b) Xuggler: http://code.google.com/feeds/p/xuggle/updates/basic

Hope that's helpful,

- Art

--
http://www.xuggle.com/
xu‧ggle (zŭ' gl) v. To freely encode, decode, and experience audio and video.

Use Xuggle to get the power of FFmpeg in Java.

_______________________________________________
Red5 mailing list
Red5@...
http://osflash.org/mailman/listinfo/red5_osflash.org