Updated 8/2/05

Okay,  I think the core code is up and running.  Here is what is happening:

I am running a program that checks the Oregon State mirror every five minutes for a new Firefox build from the Pacifica build machine.  Approximately one build per hour is being generated.  If a new build is available, I download and archive it to my hard drive.  I then upload the most recent build to the website at this location:  http://www.projects1.com/firefox/NightlyBuilds/win_zips/

Current To Do:
Now that the builds are being provided, a couple of obvious improvements seem to stand out:

1)  We should only upload builds that have changes from the previous build.  This can be accomplished by checking the tinderbox status at:  http://tinderbox.mozilla.org/showbuilds.cgi?tree=Firefox#open  a "C" for the recently completed build indicates changes have been made.  

2)  It would also be nice to query the changes made (can get there by going to the link specificed at "C").  The list of changes in the "description" box need to be dumped to a database, one field for the complete description, and another for the bug number if present.

3)  For each bug number fixed, we would want to query the bugzilla database, and provide key information on the bug:  such as product and component, description, possibly keywords, etc.

4)  lastly, we would want a nicely formatted web page to be generated and updated with the information from items 2 and 3.  Depending on the difficulty of item 3, we may decided to just do item 2 at the present time.


One other note, if you are looking for the official nightly builds from the Mozilla organization, which are avaiable for over a year and in all three supported OS's (Windows, Mac, Linux) they can be found here http://archive.mozilla.org/pub/firefox/nightly/

---------------------------------------------------
Previous updates:

Update 6/30/05 -- Several issues have come up while working on this effort.  The biggest being that I only have 350 MB of server space on this hose, with each building taking 6-7 mb, I will quickly run out of server space hosting every hourly build.  Here is the current plan to deal with this issue:

Step 1)  Host the most recent 36 hours or so (probably around 40 builds) on this server.  For regression testing, those builds probably have the most interest.  I will still have all the older builds available by request

Step 2)  I am currently trying to find a way (with my own server or something) to host every build I have archived.  This would require HUGE amounts of disk space, but probably very low bandwidth.  Several options are being pursued here.

Step 3)  One method of reducing the disk space requirements/hosting more useful builds on this server is to only host builds that have changed from the previous one.  Querying bonsia should provide this info.  

Now we have a plan, off to implement the details :) .....


Original Plan...

The purpose of this page is to host hourly firefox builds, which are extremely useful when doing regression testing and trying to narrow the regression window.

The plan is to grab each hourly build from this location:
http://mozilla.osuosl.org/pub/mozilla.org/firefox/tinderbox-builds/pacifica-trunk/

The plan will be to start with the pacifica builds.  Builds for other operating systems could be added later if there is interest and once we get the process established.  At this time I would probably plan to host the 30 or so most recent builds, it may be beneficial to be able to "archive" selected builds, but that feature will have to wait.

Anyone with ideas or suggestions on improving this effort email me at dgrimm at  mewlan  dot  com.