Having old builds still available through the web UI would be really nice, especially if they maintained the changelog. One
selling point of autobuild is as an interface with a testing team.

ie, test team reports a bug, developers say it's fixed build with counter @1100, test team fetches a new RPM @1100. That's possible right now, however they will only be able to get the very latest through the web UI. For anything older, it will require exposing the package root via some other means.

The historic packages for 'n' previous builds, along with status, logs, etc are already kept around in the build archive. So there is no technical reason why this info can't be published.

One approach is to change the organization of the web status pages, so instead of having a single top level directory with current status, we have one sub-dir per build cycle. The top directory could then contain a summary page showing status of last 'n' builds. Alternatively the top level directory could redirect to the 'current' build cycle, and a separate 'history.html' page could provide links to all archived builds.

This ought not to increase disk space usage either, since we already hardlink between the build archive & web roots.

Copyright (C) 2004-2006, the Gna! people. Posted items are owned by whoever posted them.
Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved.