Heikki Toivonen wrote:
(Moving discussion to dev with bear's permission.)
Mike Taylor wrote:
I have a windows, linux and intel-osx tbox running for the branch - you
can view the status here:
http://builds.osafoundation.org/tinderbox/Chandler_Branches/status.html
This seems wrong. Previously we had a Tinderbox page *per branch*. This
page referenced above seems to indicate we'd have a single master tbox
page for all branches. That wouldn't be very helpful. For example,
suppose we now started tboxes for multiweek branch as well. We'd have 6
machines, 3 for rs, 3 for multiweek, and the checkins column on the left
showing checkins for *all* branches, even those that don't have tboxes
running. That just seems to create confusion for branch developers.
I recommend that we return to the system we used in the past, where each
branch gets its own Tbox page. It should show information relevant to
that branch only.
I have revised my plan to take into account Heikki's point - the
recorded scripts tinderboxes are now being reported here:
http://builds.osafoundation.org/tinderbox/Chandler_rs/status.html
I'll post when I have created other tinderboxes.
thanks,
bear
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
