Several Jenkins masters that I care about have recently upgraded the Timestamper plugin to 1.10 from 1.8. This pulls in the relatively large change in 1.9 of *timestamps actually being written to the build logs* instead of handled as metadata. The "View as Plain Text" link and /consoleText urls now serve build logs with timestamps in them!
I also have code that parses Jenkins build logs, looking for specific output from various tools. The addition of timestamps has broken this detection. Complicating my situation is the fact that my code needs to be able to parse Jenkins logs from masters regardless of whether or not they are running the Timestamper plugin - so I cannot simply start checking for the timestamper's timestamps, as they may not be there. For me, the best behavior was the original behavior: when Timestamper stored the timestamps as metadata and left the build logs pure - as they were emitted during the build. I understand that *for now*, I can just downgrade the Timestamper plugin and tell people not to upgrade, but that won't work forever. Has anyone else had to contend with the Timestamper's modification of the "real" build logs conflicting with code that tries to read the logs? What did you do? Has anyone considered or asked for an option in the Timestamper plugin to choose the old behavior instead? When discussing the redesign of Timestamper, did this issue come up? If there's a more-appropriate venue to ask this question, please let me know. Thank you! -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/89cb8616-dd6d-46db-a492-99a05fd7afe0%40googlegroups.com.
