Hi Shaun,
Shaun McDonald wrote:
On 8 Feb 2007, at 12:28, Bernd Eilers wrote:
Hi there!
Status from tinderbox builds is now integrated into the
ChildWorkspace overview page. Please watch out for anything that´s
"red" there, because this means the build fails. In this case someone
should have a closer look why.
Nice :-)
It would also be an idea to include the information available from
http://termite.go-oo.org/cws_view_ready
and
http://termite.go-oo.org/cws_view_new
There are a number of platforms supported on the buildbot
infrastructure, that are currently not available on the tinderbox (and
vice versa).
Well and it´s the status on platforms which we would be interested in.
Unfortunatly tough that information (platform) is not available on the
pages you mentioned. One must click through into the individual builds
to get their platform. And the table must be parsed to get information
for an individual ChildWorkspace. Thus information to integrate into EIS
is currently kind of difficult to obtain.
Can someone enhance termite to provide URLs which would contain a
ChildWorkspace name somewhere and provide as content a HTML Code Snippet
with a table with latest status on each platform where a build has been
done?
Something like http://termite.go-oo.org/cws/<childworkspacename>
An unkown ChildWorkspace Name should just return a 404 error there.
This would be much easier to integrate into EIS than grapping
information from the pages you mentioned.
If I could get such URLs I would be happy to integrate their contents
into the CWS Overview Pages in EIS.
The other option would be to send the logs from buildbot to tinderbox
and vice versa, so that we have many views of the same data.
Also an alternative of course.
Another option would be to have the buildbot store information on the
CWS by using an EIS SOAP method to store files at a CWS which is
available. But I would prefer to have a similar integration to what we
now do with tinderbox.
A simple thing what could also be done is to have those 2 URLs you
mentioned directly somewhere in the EIS menu (let´s see how that fits).
Shaun
Kind regards,
Bernd
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]