Jenkins logs need timestamps

[Michał Sawicz]

When a job takes a long time, it's very difficult to understand where it stalls without timestamps in the logs...

[Andy Doan (doanac)]

Which jobs in particular are you wanting this done for?

[Michał Sawicz (saviq)]

-ci jobs at least, but AFAIK there's a jenkins-global plugin to add them:

https://wiki.jenkins-ci.org/display/JENKINS/Timestamper

[Alexandros Frantzis (afrantzis)]

+1

This is an issue for Mir jobs too. We are at a point where -ci and -autolanding jobs take enough time to negatively affect our workflow. It would be great if we had a way to acquire timing information about the various internal tasks. The timestamper plugin seems like a good solution.

[Alan Griffiths (alan-griffiths)]

+1

We (Mir) are waiting 2.5 - 9+ hours for CI/autolanding jobs to complete. We don't know where the time goes even at a high level:

waiting for build agents?
setting up the environment?
building the binaries?
running the tests?
reporting the result?

Without that information it is hard to know what to changed to improve matters.