Thorsten Ziehm wrote:
[... snip ...]
Hi Thorsten,
Please note that I just also learned that tests for milestones seem to
be done on tinderbox only recently for newer milestones thus for older
milestones only information for CWSs based on milestones is available in
the new TreeView in EIS.
I just got some new background information:
The way Tinderbox handles information about milestone builds is that
only information about the last 3 milestones on a masterworkspace is
being kept. Builds on milestones are repeated as long as the build
breaks on them and a patch is available.
To take that into account when defining processes on how to handle red
tinderbox status messages in EIS this means that when we would have a
case where a CWS tinderbox status
is red and the corresponding MWS milestone is too old there is no tinderbox
referrence information available for deciding on wether the problem was
already
on the master. In this case the QA might reject the CWS and ask the
owner to please
resync to a newer milestone. This should happen very rarely because we
a) mostly do resync our ChildWorkspaces to recent milestones before
sending them to QA anyway. b) most likely if there ever was a build
breaker on that old milestone it would have been fixed in the meantime
and as cloph already told patches for corresponding fixes would be
applied to the CWS before starting the build which means the CWS would
not get red in tinderbox.
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]
