Your understanding is correct, this plugin adds timestamp details to the
individual job console output logs. So, I guess it doesn't give you exactly
what you're after. You want some indication about which of the many jobs
that were running when the server crashed was the one which caused the
fa
Well yes, but correct me if I'm wrong this plug-in add information to the
Job console, no?
It's not very clear in the Plugin description...
Tks for your answer David! :)
./Fred
Le vendredi 14 août 2015 11:36:29 UTC+2, David Brown a écrit :
>
> Are you aware of the Timestamper plugin (
> https:/
Are you aware of the Timestamper plugin
(https://wiki.jenkins-ci.org/display/JENKINS/Timestamper)? We implemented
this to see where the pinch points are in some of our longer running jobs
and find it very useful.
On Thursday, 13 August 2015 22:41:54 UTC+1, Frederic Meyrou wrote:
>
> *Dear mates
*Dear mates,*
*I maintain a huge Jenkins Master server with more than 8000 jobs and 450
Slaves. *
*One of this Jobs it giving a hard time to the Master and consume all RAM
available in JVM until GC fail, and I need to restart the server... *
*Because the number of Jobs, I can't find the fau
