[haiku-development] Re: Build Factory
- From: Ingo Weinhold <ingo_weinhold@xxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Tue, 11 Nov 2008 16:38:42 +0100
On 2008-11-11 at 02:24:19 [+0100], Sikosis <sikosis@xxxxxxxxx> wrote:
> On Mon, Nov 10, 2008 at 1:29 PM, Ingo Weinhold <ingo_weinhold@xxxxxx> wrote:
[...]
> > * The page with the archived images should list the revisions (together
> > with their corresponding date) as directories, each containing the images
> > for that revision with either descriptive names or short descriptions.
> > Obviously it should not refer to partially uploaded files -- a revision
> > directory should only become available when all files have been uploaded
> > completely.
>
> Not sure how that's possible -- how do you know when a file has been
> uploaded -- unless the server uploading tells the directory that it's
> done -- that's what the Build Factory status does.
As others already mentioned uploading to another directory first and moving
when done should do the trick. If my suggestion to have a directory per
revision was implemented, a new (not publicly visible) directory would be
created first, all files uploaded to it, and finally the directory renamed.
> > * The build factory page: Could anyone be interested in the information
> > presented there? The only reason to have a look at the logs would be, when
> > the build failed, but then the split stdout and stderr logs are
> > counter-productive. A simple link to the log would suffice.
>
> So, the logs the factory produces are useless ? If so, that could save
> a lot of time in the build process if I don't need to generate them.
Well, if at all the logs would be interesting only for troubleshooting, e.g.
when an image wasn't built correctly. For that a single log file (SVN +
builds concatenated) would fully suffice. It definitely doesn't need to be
shown prominently on the website.
[...]
> >Either drop the page completely or make it more geeky (i.e. add
> >potentially useful info like the
> > commit logs for the revisions between the builds, and useless but geeky
> > info like build statistics (build time, number of objects/targets, number
> > and total size of the files on the image, etc.)) and make it less
> > prominently accessible (just via a "more info..." link on the download
> > page).
>
> If that's the sort of information you want the Factory to show, then
> great, some feedback -- I'll work on adding a bunch of those features
> in due course.
Well, let me put it this way: I only very rarely download an image. If I do,
I know the revision I want to download (maybe just the latest one) and then I
want the website to present the necessary information concisely and clearly
and allow me to navigate quickly to where I can get the image. That would be
"haiku-os.org" -> "Nightly Builds" -> "Latest image: pre-alpha (VMWare)" for
the current build or ... -> "Archived images" -> "<revision number>" ->
"pre-alpha (VMWare)" for an older revision. At any rate I wouldn't want to
see the build factory page. So at least for my use case it could be removed
altogether.
I don't know, maybe others might interested in visiting it, but probably not
with the current information on it. Regarding the commit logs, those might be
interesting to e.g. testers so they can see what bugs have been fixed or what
features have become available. Just guessing...
CU, Ingo
Other related posts:
