Hi guys, I've been trying to write a Jenkins plugin that gives me statistics about my Jenkins cluster in terms as which jobs sit in the queue the longest, which nodes have the longest queues, build duration and little bit more.
I approached the problem by implementing a QueueDecisionHandler and remembering Tasks that got queued and then implementing RunListener<Run> to see when Run's started and completed. Today I noticed that my logic is flawed. QueueDecisionHandler is not the best place to record the start of queuing because if I remember a Task there some other DescisionHandler my cancel it but I wont' get an event about it. Another reason is that even if I remember a Task then later on in RunListener putting together a Run with a Task is very heuristic. Any better ideas how to approach this problem? Maybe some other good extension point that I have not found yet or maybe a premade plugin? :) Cheers, Toomas -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
