Hi Christian,
thanks for enlightening me ... so my issues regarding tinderbox builds
don't seem to be any.
Regards
Kay
Christian Lohmaier wrote:
Hi Kay, *,
On Fri, Mar 23, 2007 at 10:33:16AM +0100, Kay Ramme - Sun Germany - Hamburg
wrote:
Christian Lohmaier 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?
You misunderstood. The delay of 7-10 day is just for the failed ones,
the dirty ones are requeued immediately.
The failed ones are only rebuilt because otherwise there would be no
logs to look at. (and since nothing changed, there is a $minage defined
in my scripts for those.
But if a failed cws gets a commit, this makes the tree "dirty" and it is
requeued immediately.
May be Utilization? (I am
more or less a fan of "continuous integration :-)
See above, a misunderstanding.
If the tree is "dirty" (i.e. has a commit after the last build), then it
is requeued without delay and you should have the results within two
days (mostly earlier, but of course depends how much other cws are
dirty/in the queue)
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,
Often enough >4 or even more than 8 hours.
which IMHO is somewhat smaller
than 7 days and could just be regarded as the timeout for changes.
See above. You misunderstood.
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.
This is being worked on currently (sending buildbot-results to
tinderbox)
ciao
Christian
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
