On Wed, 11 Jul 2012, Jay Greguske wrote:
On 07/11/2012 02:10 PM, Seth Vidal wrote:
On Wed, 11 Jul 2012, Seth Vidal wrote:
Hi,
If a build job has been sent to a builder and the builder crashes
(let's say the hw dies) - what happens to that job? Does koji send it
to another builder to work on?
I got some answers on irc - but I wanted to expand on this a bit more:
I would like to stop having to disable/enable builders in koji manually
in order to rebuild/reboot the systems.
I'd like the kojihub to check for the last time any builder checked in.
If it has not checked in in more than N minutes then it frees any task
sent to that builder and doesn't send any new tasks to it until it does
check in.
Seems like we have all the requisite information to make the hub a bit
smarter about the presence or death of a builder. Is there a significant
component of this I'm missing?
-sv
--
buildsys mailing list
[email protected]
https://admin.fedoraproject.org/mailman/listinfo/buildsys
I can't really do more than arm-chair design these days but I'd like to
see builders be a less of a manual effort too. It'd be cool if it could
handle one-time builders too, such as EC2 instances spun up to handle
load spikes.
That's pretty much what I'd like to do.Though not on EC2 - but in a CLOUD.
I'd like to be able to double-duty some buildsystems between koji and
something else. So it would be good if I didn't have to mess around
with koji admin privileges when a box goes up/down.
I spoke with dgilmore on irc a bit and he said - we'd need some sort of
monitor process that watched for the builder checkins. If a builder didn't
check in normally then look for open tasks, free them then disable the
builder until it checks back in.
-sv
--
buildsys mailing list
[email protected]
https://admin.fedoraproject.org/mailman/listinfo/buildsys
