Hi, I'm new to jenkins and new to writing plugins.
I'm trying to write and IdleTrigger that triggers a build when Jenkins has
been idle.
(its a complex use case, but essentially I want wait for everything to be
quiet before doing something.)
An IdleTrigger may not be the best way to solve this problem, but I want to
learn a little
more about Jenkins internals anyway.
I think there are (at least) two approaches:
1) Simply get all the Computers and call getIdleStartMilliseconds() to
make sure they have
all be idle.
2) Add a RunListener and possibly other Listeners to find out when jobs
start/stop.
When no jobs are running, start the idle timer. When a job starts,
kill the timer.
Conceptually, is one approach better than the other? Or is there a better
way?
Thanks.
--
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.
