Hi Kay,
On 23 Mar 2007, at 09:33, Kay Ramme - Sun Germany - Hamburg wrote:
[..]
[...]
By the way, it would be nice, to offer a buttom to retrigger
tinderbox builds, and certainly a buildbot would be nice as well.
If the tree is dirty (i.e. there were commits after the last build
started), the cws will be rebuilt automatically. If the build
failed, it
will be rebuilt after 7-10 days (to have a log available, since
old logs
get removed from the sever).
This is IMHO quite a long time, what are the reasons not to rebuild
it directly after changes have been commited? May be Utilization?
(I am more or less a fan of "continuous integration :-)
How many CWS are there at any one time open? How long does a build
take? How far behind would the box/bot be if the compilation were to
happen more often?
So not sure what you have in mind when requesting a retrigger
function.
You cannot commit and build immediately anyway (since tinderbox
slaves
use anoncvs and that has a slight delay in syncing).
This delay is AFAIK about 30-60 minutes, which IMHO is somewhat
smaller than 7 days and could just be regarded as the timeout for
changes. I mean, a rebuild would be triggered earliest 60 m after
the latest check in. In case of any later check in, the build would
be aborted and again restarted after another 60 m. I think you get
what I mean.
Recently we have been having issues with anoncvs being one, two or
maybe more days behind the developer cvs. It would be ideal if we had
a way of knowing if or when a commit has been synced to anoncvs.
buildbot is currently enhanced to send the logs to tinderbox, so when
this is done, you can trigger a buildbot build and have the logs on
tinderbox.
Sounds good.
But again: Why would a retrigger be necessary? A build will take 3-4
hours or longer, so you're surely not sitting right next to it and
wait
for it to finish... Most likely you will go home before it
finished :-)
Yes, but this is still a difference compared to 7 days. Anyway, if
I understand you right, you suggest to just re-trigger builds on
the buildbots , instead of having a button in EIS. Which is fine
for me as well, as long as I can somehow influence that tinderbox
status actually reported in EIS.
The tinderbox status doesn't state the date/time of the last build on
each tinderbox. This could be used to understand what is happening.
Also to remove confusion the idea of the text "errors: XX" would be
useful.
[..]
Shaun
___________________________________________________________
Inbox full of spam? Get leading spam protection and 1GB storage with All New Yahoo! Mail. http://uk.docs.yahoo.com/nowyoucan.html
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
