Hello Mirko, Do you mean Timestamper Plugin <https://wiki.jenkins-ci.org/display/JENKINS/Timestamper>? It stores timing information in additional files and then show it in the UI, but the original build log file (in the filesystem) remains the same. The aim of this new feature would be having the timing information just in the original build log file.
Regards, Antonio. On Mon, Sep 7, 2015 at 12:24 PM, Mirko Friedenhagen <[email protected] > wrote: > Hello Antonio, > > there is already a plugin for this. Do you want this to be part of the > core? > > Regards > Mirko > -- > Sent from my mobile > Am 07.09.2015 11:05 schrieb "Antonio Muñiz" <[email protected]>: > >> Hello, >> >> Probably by history aspects Jenkins builds log files have never used >> timestamps entries on log lines. There are some plugins that adds this >> feature, but using a kind of separate additional data, I still miss a plain >> timestamp in the log file. >> >> I see three main reasons to implement this feature: >> >> 1. Using a timestamp entry at the beginning of the line in logs is a kind >> of "standard" in the Java world (all well known loggers do it by default). >> 2. They are really useful when you have to find an issue and don't have >> access to the Jenkins UI, all you have is that log file. >> 3. Most of the logs analysis tools require a timestamp entry on each log >> line. >> >> My intention is: >> 1. Use a custom (overridden) PrintStream on StreamTaskLinstener >> 2. Provide a way to activate or deactivate this feature by configuration >> (it would be disabled by default in order to not break anything working >> before). >> >> I'm writing this, because, as I see it, it would require a core change >> (StreamTaskListener mainly and some top level configuration), so I'd like >> to know what the community thinks about it. >> >> Regards, >> Antonio. >> >> -- >> Antonio Muñiz >> Software Engineer >> CloudBees, Inc. >> >> -- >> 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]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/CAJc7kzT3L5i_oa7t%2B40J_5Z4JqGtOBE-%2BZ5Xpavf866WH05LxA%40mail.gmail.com >> <https://groups.google.com/d/msgid/jenkinsci-dev/CAJc7kzT3L5i_oa7t%2B40J_5Z4JqGtOBE-%2BZ5Xpavf866WH05LxA%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > -- > 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]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/CAK8jvqzZFQjzJtyM9GtrdviGMhFOhf%3DTRBY37vHdtrutxY4KGQ%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/CAK8jvqzZFQjzJtyM9GtrdviGMhFOhf%3DTRBY37vHdtrutxY4KGQ%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- Antonio Muñiz Software Engineer CloudBees, Inc. -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAJc7kzSPH1a%2BfD0f%2BdEO%3D%2BdDYGttE4WYQc9zdV9P1qVPyx%3DFRg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
