Thorsten Ziehm wrote:
Hi all,

Hi there!


could this the starting point that QA have to set CWS back to the CWS owner, when a result of tinderbox is red?

I think the Release Meeting or something similar should decide about a final "go" or "no-go" on that.

Then I will add this
information to the Wiki page and will link it to the QA CWS approval
process.

Good idea!


I have only one question, which is the current situation. How could
see the CWS Owner or QA Rep if the build breaker isn't also on the Master? Currently #75975# breaks the Mac builds.
http://www.openoffice.org/issues/show_bug.cgi?id=75975


This is relative easy. Tinderbox does also test the masters. But you have to navigate to those statuses via the tinderbox main page.

In EIS use the menu entry "Misc / Tinderbox Main page" or directly use the URL http://go-oo.org/tinderbox/. On the tinderbox main page you can scroll to the bottom where there is a list "Tinderbox Pages sorted by Project", this list contains every CWS and MWS recently testet. You can than click on eg. "SRC680_m210" to see the result of all the tests for the Masterworkspace SRC680m210. For the latests result of one MWS - i think this is what you really need - look out for something like "Summary Information for SRC680_m210" on that tinderbox main page and than use the "express" link below that headline. The page shown than shows first the latest build status of the MasterWorkspace and then the result of all test for CWSs created on that MasterWorkspace.

I know this is not an optimal solution yet and will see if I can find a better way to integrate results of MWS tests into EIS, stay tuned.

Kind regards,
Bernd Eilers


Thorsten


Bernd Eilers schrieb:


Hi there!

A new Wiki page for the red tinderbox status shown in EIS and what you can do if you have that to get more detailed information etc. is now available.

The Wiki Entry is at:

http://wiki.services.openoffice.org/wiki/RedTinderboxStatusInEIS

Feel free to add any useful information you have in this area there.

Kind regards,
Bernd Eilers

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to