Hi
the solution we are using is a "cron" jenkins job, running on the master
every 10min, which checks if any jobs are stuck in the build queue for a
certain amount of time (let's say 1 hour)
by using groovy build step + some jenkins java classes, it is easy to
monitor, and you can then use post-
We used a network monitoring system to raise an alarm if any job was in the
queue longer than a threshold time. We did that by reading the HTML of the
top Jenkins page and parsing the content.
It wasn't a terribly elegant solution, but it worked.
Looking back, we probably should have created a p
